App domain recycling issue in 2.0 but latest VS2003 SP1 seems to fix it - why?

[Tony]

Hi all,

Here's the link to the issue we were seeing on our ASP.NET system when
modifying, adding and deleting directories in framework 2.0.
http://blogs.msdn.com/toddca/archive...01/499144.aspx

I then tried a few of solution I found while perusing Google,
- FCNMode registry mod
- Relocating to App_Data folder to create/modify/delete directories.

No difference, behavior remained.

However, since installing the latest Visual Studio 2003 Service Pack 1 this
behavior has gone in my dev environment - or at least I believe this is the
reason, as directories are being created and deleted without the application
recycling.

I'm running Windows XP SP2
vs2003 standard edition
vs2005 standard edition upgrade
Framework 1.0, 1.1 SP1 and 2.0 rtm

Just a bit of background, The system was originally written in vs2003 but
has been converted to vs2005. I have deployed both systems on our test
win2000 server, vs2003 on framework 1.1 version works fine no problems and
will easily create and delete directories while the vs2005 conversion
running on framework 2.0 still exhibits the recycling behavior explained in
Todd Carter's link, which was exactly the same code coming from my xp dev
machine, minus the recent service pack install for vs2003.

So being a little perplexed how does a fix for an IDE directed at framework
1.1 fix the issue we were having for framework 2.0, is anyone else seeing
this behavior change after this service pack is applied - or even better can
a Microsoft representative comment? as the release note does not mention any
changes/fixes for the appdomain.

I just want to know why this is happening and whether this will be included
in a coming service pack for framework 2, as having to include vs2003 +
vs2003SP1 in our installer for each client deployment is absurd.

regards

Tony

[Kevin Jones]

I assume you've checked the obvous thing - that the app is still running
as a 2.0 app and that the 1.1 SP hasn't 'updated' the app to be 1.1?

Kevin

Tony wrote:

Hi all,

Here's the link to the issue we were seeing on our ASP.NET system when
modifying, adding and deleting directories in framework 2.0.
http://blogs.msdn.com/toddca/archive...01/499144.aspx

I then tried a few of solution I found while perusing Google,
- FCNMode registry mod
- Relocating to App_Data folder to create/modify/delete directories.

No difference, behavior remained.

However, since installing the latest Visual Studio 2003 Service Pack 1 this
behavior has gone in my dev environment - or at least I believe this is the
reason, as directories are being created and deleted without the application
recycling.

I'm running Windows XP SP2
vs2003 standard edition
vs2005 standard edition upgrade
Framework 1.0, 1.1 SP1 and 2.0 rtm

Just a bit of background, The system was originally written in vs2003 but
has been converted to vs2005. I have deployed both systems on our test
win2000 server, vs2003 on framework 1.1 version works fine no problems and
will easily create and delete directories while the vs2005 conversion
running on framework 2.0 still exhibits the recycling behavior explained in
Todd Carter's link, which was exactly the same code coming from my xp dev
machine, minus the recent service pack install for vs2003.

So being a little perplexed how does a fix for an IDE directed at framework
1.1 fix the issue we were having for framework 2.0, is anyone else seeing
this behavior change after this service pack is applied - or even better can
a Microsoft representative comment? as the release note does not mention any
changes/fixes for the appdomain.

I just want to know why this is happening and whether this will be included
in a coming service pack for framework 2, as having to include vs2003 +
vs2003SP1 in our installer for each client deployment is absurd.

regards

Tony

[Tony]

Hi Kevin,

Yes, that was one of the areas I checked before posting.

In IIS Properties ASP.NET the version is still set to 2.0.50727.

I also knew during development and having a play around in conguration that
if i ran the converted app in framework 1.1, the system would throw parser
errors (which would be due to the classes in the .apsx pages being partial
which is only supported in framework 2.0)

<snip>
Server Error in '/' Application.

Parser Error
Description: An error occurred during the parsing of a resource required to
service this request. Please review the following specific parse error
details and modify your source file appropriately.

Parser Error Message: Could not load type 'Web.Global'.

Source Error:

Line 1: <%@ Application Codebehind="Global.asax.cs" Inherits="Web.Global"
%>
Source File: D:\Dev_NET\CM\WebApp\global.asax Line: 1

--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET
Version:1.1.4322.2032
</snip>

So as a quick test I flicked it over to 1.1 and I received the above
message, returned to 2.0 and everything was up and running again.

so to reiterate, System copy running on windows 2000

framework 2.0 : definitely recycles when in run the code calling
Directory.Delete(). (still no vs2003 service pack)
framework 1.1 : no problems

my dev enviroment (prior vs2003 sp1 install) : recycled
my dev environment (post vs2003 sp1 install) : no problems.

Any other ideas? Thanks in advance.

regards

Tony

"Kevin Jones" <kj**********@develop.comwrote in message
news:up**************@TK2MSFTNGP03.phx.gbl...

>I assume you've checked the obvous thing - that the app is still running as
a 2.0 app and that the 1.1 SP hasn't 'updated' the app to be 1.1?

Kevin

Tony wrote:

>Hi all,

Here's the link to the issue we were seeing on our ASP.NET system when
modifying, adding and deleting directories in framework 2.0.
http://blogs.msdn.com/toddca/archive...01/499144.aspx

I then tried a few of solution I found while perusing Google,
- FCNMode registry mod
- Relocating to App_Data folder to create/modify/delete directories.

No difference, behavior remained.

However, since installing the latest Visual Studio 2003 Service Pack 1
this behavior has gone in my dev environment - or at least I believe this
is the reason, as directories are being created and deleted without the
application recycling.

I'm running Windows XP SP2
vs2003 standard edition
vs2005 standard edition upgrade
Framework 1.0, 1.1 SP1 and 2.0 rtm

Just a bit of background, The system was originally written in vs2003 but
has been converted to vs2005. I have deployed both systems on our test
win2000 server, vs2003 on framework 1.1 version works fine no problems
and will easily create and delete directories while the vs2005 conversion
running on framework 2.0 still exhibits the recycling behavior explained
in Todd Carter's link, which was exactly the same code coming from my xp
dev machine, minus the recent service pack install for vs2003.

So being a little perplexed how does a fix for an IDE directed at
framework 1.1 fix the issue we were having for framework 2.0, is anyone
else seeing this behavior change after this service pack is applied - or
even better can a Microsoft representative comment? as the release note
does not mention any changes/fixes for the appdomain.

I just want to know why this is happening and whether this will be
included in a coming service pack for framework 2, as having to include
vs2003 + vs2003SP1 in our installer for each client deployment is
absurd.

regards

Tony

[Kevin Jones]

Thought I'd ask the obvious question :)

Sorry, in that case I'm as stumped as you - and I haven't had to use 1.1
for a while so haven't installed the SP

Kevin

Tony wrote:

Hi Kevin,

Yes, that was one of the areas I checked before posting.

In IIS Properties ASP.NET the version is still set to 2.0.50727.

I also knew during development and having a play around in conguration that
if i ran the converted app in framework 1.1, the system would throw parser
errors (which would be due to the classes in the .apsx pages being partial
which is only supported in framework 2.0)

<snip>
Server Error in '/' Application.

Parser Error
Description: An error occurred during the parsing of a resource required to
service this request. Please review the following specific parse error
details and modify your source file appropriately.

Parser Error Message: Could not load type 'Web.Global'.

Source Error:

Line 1: <%@ Application Codebehind="Global.asax.cs" Inherits="Web.Global"
%>
Source File: D:\Dev_NET\CM\WebApp\global.asax Line: 1

--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET
Version:1.1.4322.2032
</snip>

So as a quick test I flicked it over to 1.1 and I received the above
message, returned to 2.0 and everything was up and running again.

so to reiterate, System copy running on windows 2000

framework 2.0 : definitely recycles when in run the code calling
Directory.Delete(). (still no vs2003 service pack)
framework 1.1 : no problems

my dev enviroment (prior vs2003 sp1 install) : recycled
my dev environment (post vs2003 sp1 install) : no problems.

Any other ideas? Thanks in advance.

regards

Tony

"Kevin Jones" <kj**********@develop.comwrote in message
news:up**************@TK2MSFTNGP03.phx.gbl...

>I assume you've checked the obvous thing - that the app is still running as
a 2.0 app and that the 1.1 SP hasn't 'updated' the app to be 1.1?

Kevin

Tony wrote:

>>Hi all,

Here's the link to the issue we were seeing on our ASP.NET system when
modifying, adding and deleting directories in framework 2.0.
http://blogs.msdn.com/toddca/archive...01/499144.aspx

I then tried a few of solution I found while perusing Google,
- FCNMode registry mod
- Relocating to App_Data folder to create/modify/delete directories.

No difference, behavior remained.

However, since installing the latest Visual Studio 2003 Service Pack 1
this behavior has gone in my dev environment - or at least I believe this
is the reason, as directories are being created and deleted without the
application recycling.

I'm running Windows XP SP2
vs2003 standard edition
vs2005 standard edition upgrade
Framework 1.0, 1.1 SP1 and 2.0 rtm

Just a bit of background, The system was originally written in vs2003 but
has been converted to vs2005. I have deployed both systems on our test
win2000 server, vs2003 on framework 1.1 version works fine no problems
and will easily create and delete directories while the vs2005 conversion
running on framework 2.0 still exhibits the recycling behavior explained
in Todd Carter's link, which was exactly the same code coming from my xp
dev machine, minus the recent service pack install for vs2003.

So being a little perplexed how does a fix for an IDE directed at
framework 1.1 fix the issue we were having for framework 2.0, is anyone
else seeing this behavior change after this service pack is applied - or
even better can a Microsoft representative comment? as the release note
does not mention any changes/fixes for the appdomain.

I just want to know why this is happening and whether this will be
included in a coming service pack for framework 2, as having to include
vs2003 + vs2003SP1 in our installer for each client deployment is
absurd.

regards

Tony

[Tony]

I tried a few more things on my dev machine.

Restarted IIS
iisreset /restart

checked application - no recycling

Brought up vs2005 command prompt and navigated to v2.0 folder and ran
aspnet_iisreg.exe -i

checked application - no recycling

Restarted IIS again
iisreset /restart

checked application - no recycling

The issue I was seeing is completely gone on my dev environment, but
behaviour still exists on our deployment server and the only change made was
the installation of the latest VS2003 SP1.

Is anyone else experiencing this issue with the framework 2.0 appdomain
recycling and is desperate for a solution and have yet not installed vs2003
sp1? Try installing it and see if there's a difference and let me know here.

Not only is the appdomain no longer recycling but directories are being
created as well, the deployment server running the copy doesn't even allow
that to occur - and just to recheck, they both are definitely running as
asp.net 2.0 in web application format (i.e with partial classes, so thus no
possibility to run on anything but framework 2.0).

Its a great outcome,....but puzzling as to why it has occurred.

Heres the link to vs2003 sp1 changes, maybe someone else can identify
something i may have missed.
http://support.microsoft.com/default...b;en-us;918007

regards

Tony

"Kevin Jones" <kj**********@develop.comwrote in message
news:O3**************@TK2MSFTNGP06.phx.gbl...

Thought I'd ask the obvious question :)

Sorry, in that case I'm as stumped as you - and I haven't had to use 1.1
for a while so haven't installed the SP

Kevin

Tony wrote:

>Hi Kevin,

Yes, that was one of the areas I checked before posting.

In IIS Properties ASP.NET the version is still set to 2.0.50727.

I also knew during development and having a play around in conguration
that if i ran the converted app in framework 1.1, the system would throw
parser errors (which would be due to the classes in the .apsx pages being
partial which is only supported in framework 2.0)

<snip>
Server Error in '/' Application.

Parser Error
Description: An error occurred during the parsing of a resource required
to service this request. Please review the following specific parse error
details and modify your source file appropriately.

Parser Error Message: Could not load type 'Web.Global'.

Source Error:

Line 1: <%@ Application Codebehind="Global.asax.cs"
Inherits="Web.Global" %>
Source File: D:\Dev_NET\CM\WebApp\global.asax Line: 1

--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2032;
ASP.NET Version:1.1.4322.2032
</snip>

So as a quick test I flicked it over to 1.1 and I received the above
message, returned to 2.0 and everything was up and running again.

so to reiterate, System copy running on windows 2000

framework 2.0 : definitely recycles when in run the code calling
Directory.Delete(). (still no vs2003 service pack)
framework 1.1 : no problems

my dev enviroment (prior vs2003 sp1 install) : recycled
my dev environment (post vs2003 sp1 install) : no problems.

Any other ideas? Thanks in advance.

regards

Tony

"Kevin Jones" <kj**********@develop.comwrote in message
news:up**************@TK2MSFTNGP03.phx.gbl...

>>I assume you've checked the obvous thing - that the app is still running
as a 2.0 app and that the 1.1 SP hasn't 'updated' the app to be 1.1?

Kevin

Tony wrote:
Hi all,

Here's the link to the issue we were seeing on our ASP.NET system when
modifying, adding and deleting directories in framework 2.0.
http://blogs.msdn.com/toddca/archive...01/499144.aspx

I then tried a few of solution I found while perusing Google,
- FCNMode registry mod
- Relocating to App_Data folder to create/modify/delete directories.

No difference, behavior remained.

However, since installing the latest Visual Studio 2003 Service Pack 1
this behavior has gone in my dev environment - or at least I believe
this is the reason, as directories are being created and deleted
without the application recycling.

I'm running Windows XP SP2
vs2003 standard edition
vs2005 standard edition upgrade
Framework 1.0, 1.1 SP1 and 2.0 rtm

Just a bit of background, The system was originally written in vs2003
but has been converted to vs2005. I have deployed both systems on our
test win2000 server, vs2003 on framework 1.1 version works fine no
problems and will easily create and delete directories while the vs2005
conversion running on framework 2.0 still exhibits the recycling
behavior explained in Todd Carter's link, which was exactly the same
code coming from my xp dev machine, minus the recent service pack
install for vs2003.

So being a little perplexed how does a fix for an IDE directed at
framework 1.1 fix the issue we were having for framework 2.0, is anyone
else seeing this behavior change after this service pack is applied -
or even better can a Microsoft representative comment? as the release
note does not mention any changes/fixes for the appdomain.

I just want to know why this is happening and whether this will be
included in a coming service pack for framework 2, as having to include
vs2003 + vs2003SP1 in our installer for each client deployment is
absurd.

regards

Tony

[nadersoliman]

Hi,

Are you sure it solved your problem? I still have the problem in action

The method I use to monitor the issue can be found here

http://weblogs.asp.net/scottgu/archi...14/433194.aspx

I hope you can use it and tell us what you find.

BTW, I have contacted Microsfot support and got the fix for the
following knowledge base article

http://support.microsoft.com/kb/913297/en-us

but it didn't fix anything and I have to play around with the FCNMode
to get things going on my dev box.

Regards,
Nader