Last post Mar 30, 2008 01:35 PM by onor
Mar 27, 2008 01:59 PM|onor|LINK
The odd thing is that signatures on others' components (also managed code) in the same installer project are still there after installation. I guess the VS build somehow modifies (adds info?) the components in a way that invalidates the signatures.
The solution consist of 5 library projects, one web project, and the deployment project. I run 2 separate builds, first one building all but the deployment project (then sign the built components), then one building only the deployment project. Finally,
I sign the .msi.
The problem is consistent, on several computers, both with VS2005/2008.
I was about to try our copy of InstallShield Express 2008 (for VS2005), but i realize that it does not yet support VS2008.
Because of this we are stuck in our process of getting "Works with Windows Server 2008" for our applications.
Would really appreciate some ideas..
Mar 28, 2008 11:22 AM|onor|LINK
Some more info:
This is a project based on the template "ASP.NET Web Application". That is, NOT a project based on the template "ASP.NET Web Site". For deployment, within the same solution, I'm selecting: Menu File, Add, New Project, choosing the template "Web Setup Project".
(actually, I recreated this setup project in VS2008 since it didn't convert and didn't work properly otherwise)
I tried not signing the installer (that is I build components, sign then, build the installer, then SKIP signing the installer). Problem remains.
I've tried build from command line, no help. (but did I miss some switches?)
It kind of looks like it is "impossible" to meet the requirements of "Works with Windows Server 2008" for a "ASP.NET Web Application" using a installer (manual install is actually an alternative..), since we must:
We could select the option Package Files "As loose uncompressed files", but I'm not sure we'll meet requirement 1. in that way.
Mar 30, 2008 01:35 PM|onor|LINK
Ok, found it.
Changed the subject on this post, my mistake. Signatures were never removed after all, it turned out that I have signed the wrong dll copies!
More testing revealed that my deployment project did not pack my DLLs from it's reported source path, but used these locations
I sure would have loved to find this information in an article!
I also learned that I must choose the right solution configuration at all times. It seems that right-clicking a project in the solution explorer does not always work the way I hoped. It seems to build files of the active configuration even if this
right-clicked project is not part of it.
To the administrator: I think you may have moved my post to the the wrong forum.
I have not used the "VS Web Deployment Projects". I beleive this deployment project type is for projects of type "ASP.NET Web Site"
only. I must use the "Web Setup Project" with my "ASP.NET Web Application". Please correct me if I'm wrong.
Any writers here? Would like to buy a book with detailed info on the Web Setup Project. Would like to stay more in control without spending a whole lot of tile experimenting. We purchased the InstallShield Express, but for my scenario it
seemed to introduce more complications than it solved, compared with the Web Setup Project.
Anyway, things are actually working now!