Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / General / September 2005

Tip: Looking for answers? Try searching our database.

dll are locked

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Shimon Sim - 31 Aug 2005 01:30 GMT
I always bump in the same problem while working with VS.NET - ASP.NET
projects with class library. It returns me that some of my resulting dll are
used by some other processes.
I don't know which processes are using those dlls but restarting VS always
helps. Some times I need to restart it 3 times a day or more.
Today it was already forth.
Any solution for this annoyance?
Thanks
Shimon
"Gary Chang[MSFT]" - 31 Aug 2005 09:04 GMT
Hi Shimon,

Based on your description, I think the problem is that you may have the
ASP.NET project and the class library project in a VS2003 solution, when
you want to update and build the assembly of the class library project, the
VS.NET IDE popup the warning message that the target dll is being used by
some other processes. Please correct me if I have misunderstood anything.

If so, would you please tell me how does your ASP.NET project reference the
class library project's assembly, by project reference?

And is the referenced assembly strong named?

Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.
Shimon Sim - 31 Aug 2005 17:17 GMT
Thank you for the answer.
I think that you understood my scenario correctly.
I reference my class library by project reference and the assemblies are not
strong named.
Thanks you
Shimon.
> Hi Shimon,
>
[quoted text clipped - 25 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
"Gary Chang[MSFT]" - 01 Sep 2005 07:04 GMT
Hi Shimon,

>I reference my class library by project reference and the
>assemblies are not strong named.

If so, such behavior is as expected, the referenced assembly is just being
locked by the VS.NET IDE(it is still being used by your ASP.NET project
which belongs to the current solution.)

In this scenario, I suggest you can exclude that class library project from
the ASP.NET project's solution or don't use the project reference, just the
reference the target assembly directly...

Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.
Shimon Sim - 01 Sep 2005 14:43 GMT
But I need to use debug version of the class library when I am using debug
version of ASP..NET  project and release version when  I am building for
release.
How do I accomplish this without referencing the project?
Shimon
> Hi Shimon,
>
[quoted text clipped - 25 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
"Gary Chang[MSFT]" - 02 Sep 2005 09:00 GMT
Hi Shimon,

>But I need to use debug version of the class library when
>I am using debug  version of ASP..NET  project and
>release version when  I am building for release.
>How do I accomplish this without referencing the project?

This could not be done without referencing the project, but If you just
want to your ASP.NET project uses the latest build version of the target
assembly, I suggest you may try the following workaround without the
referencing the class library project directly:

Specify the class library's Output Path property to your ASP.NET project's
bin directory:

YourAsssemblyProject Property Pages/Cinfiguration
Properties/Build/Outputs/Output Path

Whis this helps!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.
Shimon Sim - 02 Sep 2005 13:15 GMT
Thank you Gary
Shimon
> Hi Shimon,
>
[quoted text clipped - 28 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
"Gary Chang[MSFT]" - 03 Sep 2005 03:30 GMT
You are welcome Shimon!

I am glad to help you on this issue and appreciate your understanding with
this VS2003 IDE's behavior.

Have a nice weekend!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.
Shimon Sim - 01 Sep 2005 17:39 GMT
I was trying to make some research on this. Everything I found is exactly
what I am doing - referencing project.
Why no one ever mentions about this behavior and shows other approach?
This is strange.
Shimon.

> Hi Shimon,
>
[quoted text clipped - 25 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.