running "aspnet_reg iis -i" during install

[=?Utf-8?B?RGF2aWQgVGhpZWxlbg==?=]

Hi;

How are we supposed to handle this. It appears that this must be run on a
system for an ASP.NET app to run. On WinXP we are finding that the user
ASPNET does not exist until this is run.

However, running this impacts all existing ASP.NET apps and sets the default
..NET for all new ones. So if we run this we can screw up all the ASP.NET apps
already on a system.

How should we handle this in our installer?

--
thanks - dave
david_at_windwa rd_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm

[Brennan Stehling]

David,

WinXP runs IIS 5 with the application pool running as ASPNET while on
Windows 2003 Server with IIS 6 the default application pool runs as
Network Service. So that could trip you up when you deploy your web
application.

To automate what you want to do with IIS you can use the MSBuild
Community Tasks which do work with IIS.

http://msbuildtasks.tigris.org/

To get started with MSBuild you can read this series I wrote which has
examples you can use directly...

http://brennan.offwhite.net/blog/200...ps-to-msbuild/

Brennan Stehling
http://brennan.offwhite.net/blog/

David Thielen wrote:

Hi;

How are we supposed to handle this. It appears that this must be run on a
system for an ASP.NET app to run. On WinXP we are finding that the user
ASPNET does not exist until this is run.

However, running this impacts all existing ASP.NET apps and sets the default
.NET for all new ones. So if we run this we can screw up all the ASP.NET apps
already on a system.

How should we handle this in our installer?

--
thanks - dave
david_at_windwa rd_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm

[Walter Wang [MSFT]]

Hi Dave,

What do you mean by "ASPNET does not exist"? Do you mean it's deleted by
user after ASP.NET is installed?

I understand that you want to automate the configuration of your ASP.NET
web site in IIS. Using "aspnet_reg iis -i" will upgrade old versions of
asp.net web site to updated version, which might have impact on existing
web sites, therefore you don't want to call aspnet_regiis -i in your
installer.

If ASP.NET is installed and configured correctly in the root web site, you
could use aspnet_regiis -s to configure your web site only, for example:

aspnet_regiis -s W3SVC/1/ROOT/mywebsite
Sincerely,
Walter Wang (wa****@online. microsoft.com, remove 'online.')
Microsoft Online Community Support

=============== =============== =============== =====
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications. If you are using Outlook Express, please make sure you clear the
check box "Tools/Options/Read: Get 300 headers at a time" to see your reply
promptly.

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/subscripti...t/default.aspx.
=============== =============== =============== =====

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

[Walter Wang [MSFT]]

To avoid upgrading other web sites:

If you're redistributing the .NET 2.0 redist package, pass /noaspupgrade
command line parameters so that it will only install ASP.NET 2.0 but do not
update all web sites' script mapping. If you're calling aspreg_regiis.e xe
-i, change it to -ir switch. You will then have to use aspnet_regiis -s or
-sn to manually update a web site's script mapping:

#Managing Multiple Versions of ASP.NET
http://msdn2.microsoft.com/en-us/lib...9b(VS.80).aspx
To prevent the installation from automatically updating the script maps of
other applications on the computer, use the /noaspnetupgrade option when
issuing the Dotnetfx.exe command. This option causes the setup program to
use the -ir option of Aspnet_regiis.e xe instead, which skips the automatic
script map updates, default documentation, and MIME swapping steps.

Regards,
Walter Wang (wa****@online. microsoft.com, remove 'online.')
Microsoft Online Community Support

=============== =============== =============== =====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=============== =============== =============== =====

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

[=?Utf-8?B?RGF2aWQgVGhpZWxlbg==?=]

Ok, half way there.

For Windows 2003 this solves it.

For WinXP I get the message that ASPNET is not a user if I use -ir. If I use
-i then it does work. I am getting this message when setting access to a
created directory in the installer.

Any ideas?

--
thanks - dave
david_at_windwa rd_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm


"Walter Wang [MSFT]" wrote:

To avoid upgrading other web sites:

If you're redistributing the .NET 2.0 redist package, pass /noaspupgrade
command line parameters so that it will only install ASP.NET 2.0 but do not
update all web sites' script mapping. If you're calling aspreg_regiis.e xe
-i, change it to -ir switch. You will then have to use aspnet_regiis -s or
-sn to manually update a web site's script mapping:

#Managing Multiple Versions of ASP.NET
http://msdn2.microsoft.com/en-us/lib...9b(VS.80).aspx
To prevent the installation from automatically updating the script maps of
other applications on the computer, use the /noaspnetupgrade option when
issuing the Dotnetfx.exe command. This option causes the setup program to
use the -ir option of Aspnet_regiis.e xe instead, which skips the automatic
script map updates, default documentation, and MIME swapping steps.

Regards,
Walter Wang (wa****@online. microsoft.com, remove 'online.')
Microsoft Online Community Support

=============== =============== =============== =====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=============== =============== =============== =====

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

[=?Utf-8?B?RGF2aWQgVGhpZWxlbg==?=]

I think it may be the order we do this in - we need to call aspnet_regiis -ir
BEFORE we set the folder permissions. Will let you know how it goes.

--
thanks - dave
david_at_windwa rd_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm


"David Thielen" wrote:

Ok, half way there.

For Windows 2003 this solves it.

For WinXP I get the message that ASPNET is not a user if I use -ir. If I use
-i then it does work. I am getting this message when setting access to a
created directory in the installer.

Any ideas?

--
thanks - dave
david_at_windwa rd_dot_net
http://www.windwardreports.com

Cubicle Wars - http://www.windwardreports.com/film.htm


"Walter Wang [MSFT]" wrote:

To avoid upgrading other web sites:

If you're redistributing the .NET 2.0 redist package, pass /noaspupgrade
command line parameters so that it will only install ASP.NET 2.0 but do not
update all web sites' script mapping. If you're calling aspreg_regiis.e xe
-i, change it to -ir switch. You will then have to use aspnet_regiis -s or
-sn to manually update a web site's script mapping:

#Managing Multiple Versions of ASP.NET
http://msdn2.microsoft.com/en-us/lib...9b(VS.80).aspx
To prevent the installation from automatically updating the script maps of
other applications on the computer, use the /noaspnetupgrade option when
issuing the Dotnetfx.exe command. This option causes the setup program to
use the -ir option of Aspnet_regiis.e xe instead, which skips the automatic
script map updates, default documentation, and MIME swapping steps.

Regards,
Walter Wang (wa****@online. microsoft.com, remove 'online.')
Microsoft Online Community Support

=============== =============== =============== =====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=============== =============== =============== =====

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