.NET 1.1 exe remains in-use after exit

  • Thread starter Thread starter SYNC/Anang
  • Start date Start date
S

SYNC/Anang

Hello.

I'm testing Vista build 5384. When I run a .NET 1.1 from
a mapped network drive, even after I exit the program,
it remains in-use; prevent me to replace the file or
delete it. I had to release it from remote computer's
administrator tool.

This behavior doesn't occur on .NET 2.0 files. Any idea,
or workaround? Thank you.
 
Hi,

My hunch is this is both off-topic (maybe try "vista.file_management" or
"vista.general' newsgroups)... and it appears to be a .NET Framework issue.

Memory locking/allocation has changed between .NET 1.x and 2.0, so I would
bet that it is a .NET 1.1 issue (remote-accessing of files).

- naseru
 
Hello,

Thank for the reply.

Because this behavior occurs only on Vista and not on other OS (XP, W2K3),
I think it is a Vista issue, yet with .NET 1.1 of course.

The application is just a simple windows application. Built from scratch,
includes only a single button that open a connection to a SQL server using
a single SqlConnection object. No command or other codes. Just as simple as
that to produce the behavior. Just push the button, exit, and the file
will be remain in-use/open on the remote computer.

I know that it might be not appropriate to post in this newsgroup, but
I couldn't find other which fits more.


Naseru said:
Hi,

My hunch is this is both off-topic (maybe try "vista.file_management" or
"vista.general' newsgroups)... and it appears to be a .NET Framework issue.

Memory locking/allocation has changed between .NET 1.x and 2.0, so I would
bet that it is a .NET 1.1 issue (remote-accessing of files).

- naseru
Click to expand...
 
Have you installed the latest service pack for .NET 1.1?
--
--
Andre
Windows Connected | http://www.windowsconnected.com
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta

SYNC/Anang said:
Hello,

Thank for the reply.

Because this behavior occurs only on Vista and not on other OS (XP, W2K3),
I think it is a Vista issue, yet with .NET 1.1 of course.

The application is just a simple windows application. Built from scratch,
includes only a single button that open a connection to a SQL server using
a single SqlConnection object. No command or other codes. Just as simple
as
that to produce the behavior. Just push the button, exit, and the file
will be remain in-use/open on the remote computer.

I know that it might be not appropriate to post in this newsgroup, but
I couldn't find other which fits more.
Click to expand...
 
Back
Top