By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
432,188 Members | 834 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 432,188 IT Pros & Developers. It's quick & easy.

Do not deploy the source code files

P: n/a
Hi,

I have developed a a web application with ASP.NET 2.0 and VS 2005.
My client wants to be delivered a .msi file that installs the app. My big
problem is that the .msi also deploys the source code files which I strongly
don't want to happen.

How to create a setup project that does not include the source files but
only the aspx, config and some binaries (as it was with VS 2003 setup
projects)?

Thank you,
Mircea

Feb 1 '07 #1
Share this Question
Share on Google+
5 Replies


P: n/a
"Mircea Pleteriu" <mp*******@ecom-webfactory.dewrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl...
How to create a setup project that does not include the source files but
only the aspx, config and some binaries (as it was with VS 2003 setup
projects)?
http://www.google.co.uk/search?sourc...oyment+Project
Feb 1 '07 #2

P: n/a
Use the Web Deployments Project add-in for VS:

Download:
http://msdn2.microsoft.com/en-us/asp.net/aa336619.aspx

Usage hints:
http://msdn2.microsoft.com/en-us/library/aa479568.aspx


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Mircea Pleteriu" <mp*******@ecom-webfactory.dewrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl...
Hi,

I have developed a a web application with ASP.NET 2.0 and VS 2005.
My client wants to be delivered a .msi file that installs the app. My big problem is that the .msi
also deploys the source code files which I strongly don't want to happen.

How to create a setup project that does not include the source files but only the aspx, config
and some binaries (as it was with VS 2003 setup projects)?

Thank you,
Mircea

Feb 1 '07 #3

P: n/a
I've installed the tool.
At a first glance it seems that this tool does not generate .msi or merge
modules..
And I need a msi or merge module.
"Juan T. Llibre" <no***********@nowhere.comwrote in message
news:e3**************@TK2MSFTNGP04.phx.gbl...
Use the Web Deployments Project add-in for VS:

Download:
http://msdn2.microsoft.com/en-us/asp.net/aa336619.aspx

Usage hints:
http://msdn2.microsoft.com/en-us/library/aa479568.aspx


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Mircea Pleteriu" <mp*******@ecom-webfactory.dewrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl...
>Hi,

I have developed a a web application with ASP.NET 2.0 and VS 2005.
My client wants to be delivered a .msi file that installs the app. My big
problem is that the .msi also deploys the source code files which I
strongly don't want to happen.

How to create a setup project that does not include the source files but
only the aspx, config and some binaries (as it was with VS 2003 setup
projects)?

Thank you,
Mircea


Feb 1 '07 #4

P: n/a
It does.

Review the hints at :
http://msdn2.microsoft.com/en-us/library/aa479568.aspx

You need to add a “Web Setup” project into your WDP solution.

This is a standard VS 2005 project type that supports packaging a .msi file
along with logic to create a vroot and deploy an application when executed.

You can easily configure the WebSetup project to pipe in
the output from your WebSiteDeployment project into the MSI.

Then, while you select “Build Solution” again you’ll build your web deployment project,
pipe it into the setup project, and you’ll be left with a .MSI setup program for your web
application
that will walk you through creating an IIS vroot and deploy your production app on a web server when
run.

There's specific instructions for doing that, with images, at :
http://weblogs.asp.net/scottgu/archi...06/429723.aspx


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Mircea Pleteriu" <mp*******@ecom-webfactory.dewrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...
I've installed the tool.
At a first glance it seems that this tool does not generate .msi or merge modules..
And I need a msi or merge module.
"Juan T. Llibre" <no***********@nowhere.comwrote in message
news:e3**************@TK2MSFTNGP04.phx.gbl...
>Use the Web Deployments Project add-in for VS:

Download:
http://msdn2.microsoft.com/en-us/asp.net/aa336619.aspx

Usage hints:
http://msdn2.microsoft.com/en-us/library/aa479568.aspx


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Mircea Pleteriu" <mp*******@ecom-webfactory.dewrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl...
>>Hi,

I have developed a a web application with ASP.NET 2.0 and VS 2005.
My client wants to be delivered a .msi file that installs the app. My big problem is that the
.msi also deploys the source code files which I strongly don't want to happen.

How to create a setup project that does not include the source files but only the aspx, config
and some binaries (as it was with VS 2003 setup projects)?

Thank you,
Mircea



Feb 1 '07 #5

P: n/a
It works.
Thank you lots.

"Juan T. Llibre" <no***********@nowhere.comwrote in message
news:%2***************@TK2MSFTNGP05.phx.gbl...
It does.

Review the hints at :
http://msdn2.microsoft.com/en-us/library/aa479568.aspx

You need to add a "Web Setup" project into your WDP solution.

This is a standard VS 2005 project type that supports packaging a .msi
file
along with logic to create a vroot and deploy an application when
executed.

You can easily configure the WebSetup project to pipe in
the output from your WebSiteDeployment project into the MSI.

Then, while you select "Build Solution" again you'll build your web
deployment project,
pipe it into the setup project, and you'll be left with a .MSI setup
program for your web application
that will walk you through creating an IIS vroot and deploy your
production app on a web server when run.

There's specific instructions for doing that, with images, at :
http://weblogs.asp.net/scottgu/archi...06/429723.aspx


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Mircea Pleteriu" <mp*******@ecom-webfactory.dewrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...
>I've installed the tool.
At a first glance it seems that this tool does not generate .msi or merge
modules..
And I need a msi or merge module.
"Juan T. Llibre" <no***********@nowhere.comwrote in message
news:e3**************@TK2MSFTNGP04.phx.gbl...
>>Use the Web Deployments Project add-in for VS:

Download:
http://msdn2.microsoft.com/en-us/asp.net/aa336619.aspx

Usage hints:
http://msdn2.microsoft.com/en-us/library/aa479568.aspx


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Mircea Pleteriu" <mp*******@ecom-webfactory.dewrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl.. .
Hi,

I have developed a a web application with ASP.NET 2.0 and VS 2005.
My client wants to be delivered a .msi file that installs the app. My
big problem is that the .msi also deploys the source code files which I
strongly don't want to happen.

How to create a setup project that does not include the source files
but only the aspx, config and some binaries (as it was with VS 2003
setup projects)?

Thank you,
Mircea





Feb 1 '07 #6

This discussion thread is closed

Replies have been disabled for this discussion.