Assembly name pb in test mode for web site in VS2005

[WT]

Hello,
We have a license system that checks the assembly name and version using
..NETLicenseManager API (Cf Nikhil K. book on server controls) , using a
deployment project we are able to set the assmbly name and version for
resulting dll, and it works ok.
But in dev phase, our assembly name is automatically generated without
possibility of control and it is very uneasyto work with, solution should be
to put #if everywere the license is tested or the assembly name is get from
..net, but this practice doesn't allow real testing.
So what to do: something has been broken here going from 1.1 to 2.0.

CS

[Ken Cox - Microsoft MVP]

Hi,

It sounds like you'd be better of going back to the old project model with
fixed assembly names. Microsoft is just releasing an add-in that looks after
all that.

"The compilation system uses a standard MSBuild based compilation process."

Visual Studio 2005 Web Application Projects (RC1)

"Web Application Projects provide a companion web project model that can be
used as an alternative to the built-in Web Site Project in Visual Studio
2005. This new model is ideal for web site developers who are converting a
Visual Studio .Net 2003 web project to Visual Studio 2005. "

http://msdn.microsoft.com/asp.net/re...p/default.aspx

Ken
Microsoft MVP [ASP.NET]

"WT" <[e-mail]> wrote in message
news:O$*************@TK2MSFTNGP05.phx.gbl...

Hello,
We have a license system that checks the assembly name and version using
.NETLicenseManager API (Cf Nikhil K. book on server controls) , using a
deployment project we are able to set the assmbly name and version for
resulting dll, and it works ok.
But in dev phase, our assembly name is automatically generated without
possibility of control and it is very uneasyto work with, solution should
be to put #if everywere the license is tested or the assembly name is get
from
.net, but this practice doesn't allow real testing.
So what to do: something has been broken here going from 1.1 to 2.0.

CS