2.0 Assembly Information - how?

[Guest]

In vs.net 2005 web apps, now that we no longer have the assemblyinfo file,
how do we set assembly information (such as version,description,company, etc)?
Thanks, Mark

 

[Scott Allen]

Mark:

This is one of the scenarios the Web Deplyoment project is designed to
handle:
http://msdn.microsoft.com/asp.net/reference/infrastructure/wdp/default.aspx

HTH,

 

[Mark Rae]

This is one of the scenarios the Web Deplyoment project is designed to
handle:
http://msdn.microsoft.com/asp.net/reference/infrastructure/wdp/default.aspx

I'm due to start investigating this soon. Does it allow deployment to a
remote web server, or just to a local file system?

Also, does it allow individual files and / or folders to be excluded from
the deployment?

 

[Guest]

Thanks Scott.
I dont think I understand. Are you saying that in vs.net 2005 I cant set
the version unless I use this tool?

 

[Scott Allen]

I'm due to start investigating this soon. Does it allow deployment to a
remote web server, or just to a local file system?

It's more for 'packaging' a web site on the local file system. You can
manage configuration settings and 'prep' everything for the
deployment.

Also, does it allow individual files and / or folders to be excluded from
the deployment?

Yes, I believe so...

 

[Scott Allen]

Thanks Scott.
I dont think I understand. Are you saying that in vs.net 2005 I cant set
the version unless I use this tool?

Well, all of the assemblies that ASP.NET will generate have no version
numbers. This is true even for 1.1, but in 1.1 ASP.NET only generated
assemblies for aspx, ascx files. In 1.1 Visual Studio compiled all of
our code-behind files into a single assembly, and we could apply
version numbers to that single assembly.

The web deployment projects take all of the assemblies the ASP.NET
compiler generates and merges them into a single assembly. It will
merge any version attributes into that assembly, too.

 

[Mark Rae]

It's more for 'packaging' a web site on the local file system. You can
manage configuration settings and 'prep' everything for the
deployment.

Er, OK - but I then have to do the deployment manually...? IMO, this seems a
*huge* step back from the previous version...

Yes, I believe so...

Great! How...?

 

[Scott Allen]

Er, OK - but I then have to do the deployment manually...? IMO, this seems a
*huge* step back from the previous version...

From the Setup & Deployment projects? Yes, they did quite a bit. There
is always the Publish feature in VS 2005. I'm going the route of
customizing the MSBUILD task because there is a tremendous amount of
flexibility. See: http://dougrohm.com/articles/11.aspx

Great! How...?

Add an ItemGroup with an ExcludeFromBuild inside. There is an example
here:
http://msdn.microsoft.com/library/en-us/dnaspp/html/web_deployment_projects.asp

 

[Mark Rae]

From the Setup & Deployment projects? Yes, they did quite a bit. There
is always the Publish feature in VS 2005. I'm going the route of
customizing the MSBUILD task because there is a tremendous amount of
flexibility. See: http://dougrohm.com/articles/11.aspx

Very interesting article.

Add an ItemGroup with an ExcludeFromBuild inside. There is an example
here:
http://msdn.microsoft.com/library/en-us/dnaspp/html/web_deployment_projects.asp

Perfect! Just what I've been looking for!

 

[Tod Birdsall, MCSD for .NET]

Hi Mark,

While doing research on MSBuild for my own projects, I compiled a list
of usefull MSBuild resources that I found to be helpful.

http://www.tod1d.net/blog/2005/12/msbuild-turorials-and-resources.html

Enjoy.

 

[Mark Rae]

Todd,

While doing research on MSBuild for my own projects, I compiled a list
of usefull MSBuild resources that I found to be helpful.

http://www.tod1d.net/blog/2005/12/msbuild-turorials-and-resources.html

Enjoy.

Thanks very much - very useful.

IMO, Microsoft really dropped the ball on the "web publish" functionality in
ASP.NET 2, and the new web deployment projects have come a long way to
address that.

The ability to have more than one deployment project in the same solution is
excellent, and the ability to replace individual parts of web.config is
little short of revolutionary.

The ItemGroup / ExcludeFromBuild functionality is a lot more cumbersome than
the "Exclude From Project" functionality in v1.1, but at least it works.

HOWEVER, the lack of ability to publish directly to the web is still
extremely irritating. IMO... That's pretty much the only major piece of
functionality missing or, at least, I haven't found a way of doing it yet...