StrataFrame Forum » StrataFrame Application Framework - V1 » Issues » Click Once Deployment and StrataFrame

Click Once Deployment and StrataFrame

Paul Chase — Fri, 30 Jun 2006 12:49:55 GMT

I am having an issue with click once deployment and strataframe. For some reason with a strataframe project it pulls in all kinds of extra dlls that a standard windows project does not.

I have excluded these "extra" dlls as was recomended in another post however I still cannot get the install to run as it errors with a message that it needs envdte80.dll. It does not matter if I mark it included or excluded it simply will not install using one touch. I googled up this Dll and it looks like it is used for VS add-ins

This only happens with a strataframe project.

For example create a new strataframe project and go to directly to publish then application files and there are quite a few referenced files added. Do the same this with a standard winforms project and you will notice that all these references are not there.

I would guess the stataframe.dll's have references to these other dll's and that is why they are pulling these into the click once deployment however I cannot figure out why I cannot exclude them and get an install to run.

Any help would be appreciated

I am using ver 1.40

Thanks Paul

RE: Click Once Deployment and StrataFrame

StrataFrame Team — Fri, 30 Jun 2006 12:49:55 GMT

Excellent. 1.4.1 should move from pre-release to full at or around Aug 1st, so, let's hope it's a little before :)

RE: Click Once Deployment and StrataFrame

Paul Chase — Fri, 30 Jun 2006 10:52:32 GMT

Thanks for the reply Ben. I am in a testing phase currently with a target go live date of August 1st so I have a bit of time until I need to deploy for production. I will try the pre-release in the meantime.

Paul

RE: Click Once Deployment and StrataFrame

StrataFrame Team — Fri, 30 Jun 2006 10:22:11 GMT

Yes, Paul, many of the type editors were directly referenced by the StrataFrame assemblies, and the type editors themselves referenced EnvDTE.dll. In 1.4.1, we removed the references to those type editors and instead referenced them by name. So, 1.4.1 has resolved the issue with the extra DLLs being brought into the solution. There are still a couple Microsoft.SqlServer dlls that are used by the Connection String Wizard, but we are working on removing those as well. If you cannot get the Click-Once to exclude those DLLs, then you'll need to upgrade to 1.4.1, and it's up to you whether you want to wait until it's a full release (it's still pre-release right now).