Files deployed by Web Deployment project

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Nadav Popplewell - 21 Feb 2007 15:04 GMT

Hi Everybody,

I'm using a Web Deployment project to create a Web Setup for a Web
Application Project I've got, and I've noticed thay the Web Deployment
Project deploys a lot of files that I'm not sure are needed...

The files are:

<project>.csproj
<project>.csproj.user
<project>.csproj.vspscc
vwd.webinfo
mssccprj.scc
*.rpt ( crystal reports that are compiled as embeded resources!)
*.xsd/*.xsc/*.xss
plus files under obj directory - in my case several dlls(not all!) and
another copy of the *.rpt files.

Is this a bug in the Web Deployment project?

Thanks,
Nadav

Reply to this Message

Steven Cheng[MSFT] - 22 Feb 2007 07:14 GMT

Hello Nadav,

Regarding on the unnecessary files copied when create websetup from a web
deployment project that referencing a web application project, it is
because "web deployment project " and "web application project" are not
designed to use together , they're of different purpose for developing
ASP.NET 2.0 application.

When Visual Studio 2005 initially release, it only support "web site"
application model for ASP.NET 2.0 and in such model, ASP.NET application is
projectless(no project files or other project setting files), all the code
are not automatically precompiled like ASP.NET 1.1 project. Also, the
built-in precompilation/publish website has limited customization options
on the precompiled web application. Therefore, the ASP.NET dev team work
out a web deployment project that can help provide more options for
precompile application developed through web site application.

For "Web Application Project", it is designed for those developers who
prefer the ASP.NET 1.X/VS 2003 project model, all the code(both ourselves
or designer generated) are display in IDE and will generate precompiled
assemblies when build the application/project. Also, there are project (and
related setting) files in Web application project.

for deployment/setup project, you can directly use the primary output from
Web application project. if you use web deployment project to precompile
web application project, since it doesn't have sense of those project model
specific files(such as csproj, xsd /xss....), it will just simply keep it
there. That's why you'll see those files from the web deployment project's
output.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

==================================================

Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

Reply to this Message

Nadav Popplewell - 22 Feb 2007 08:24 GMT

Hi Steven,

> for deployment/setup project, you can directly use the primary output from
> Web application project. if you use web deployment project to precompile
> web application project, since it doesn't have sense of those project model
> specific files(such as csproj, xsd /xss....), it will just simply keep it
> there. That's why you'll see those files from the web deployment project's
> output.

Ok, I can understand this.
But how do you create a setup for a WAP?

I tried to create a Web Setup project and use it to install a WAP.
I had to add the primary output and the conteft files.
Then I had to manually move the primary output and all the dependency dlls
to the bin directory.
Then you end up with a web site that works, but contains all the code for
all the as?x files...

Is there another way to create a setup for a WAP?

Thanks,
Nadav

Reply to this Message

Steven Cheng[MSFT] - 23 Feb 2007 08:47 GMT

Thanks for your reply Nadav,

I've tested the case you mentioend, yes, when you use Web Application
Project, and reference its output in Web Setup project's root "web
application folder", it will pull all the precompiled and referenced
assemblies there, but not the content. This is because Web Application
Project's primary output is only assemblies(application's main assembly and
other referenced assembly). You can check the web application project's
"Build" setting, the output path is ".\bin" which means primary output is
all those stuff in the bin dir.

For your scenario, if you want to create web setup project for Web
Application project, you can configure the file system(in the web setup
project) as below:

** In the "Web Application Folder", instead of add "Primary output", you
should choose the "Content Files" from the Web application Project Source.

** In the "bin" sub dir of the setup project file system, you add the
"Primary output"( and any other localized statllite assemblies if you have)
from web application project into it.

thus, when you build the setup package, those content files(aspx, ascx
...) will be put into target application's root directory while the
assemblies(primary output) will be put into the target "bin" dir as
expected.

This is what we should take care when create setup project by referencing
source of a Web Application Project.

Hope this helps some. If there is anything else we can help, please feel
free to post here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

This posting is provided "AS IS" with no warranties, and confers no rights.

Reply to this Message

Nadav Popplewell - 27 Feb 2007 09:28 GMT

Hi Steven,

Thanks for your reply,

I can do that (I have to see what is better - deploying precompiled web site
with some extra files or deploying uncompiled web site...)

I think that even if I change the setup project to reference the WAP
directly I will still leave the web deploy projects in the solution.
I've found that the precompilation catches some compilation errors that
otherwise are only reported when the user tries to access the page where the
problem is..

I hope that in the future MS will add the option to deploy precompiled WAP.

Thanks,
Nadav

Reply to this Message

Steven Cheng[MSFT] - 28 Feb 2007 08:35 GMT

Thanks for your reply Nadav,

Sure, this is a reasonable suggestion and you're recommend to submit it
over MSDN product feedback center:

http://connect.microsoft.com/feedback/default.aspx?SiteID=210

Thanks again for your feedback.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

This posting is provided "AS IS" with no warranties, and confers no rights.

Reply to this Message

Rate this thread:

Files deployed by Web Deployment project

Free Magazines