473,385 Members | 1,320 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,385 software developers and data experts.

Bizarre and annoying compiler error message.

I have a VS 2003 C# project, web app with a bunch of DLL's. When I compile
my project I often times get this message:

Unexpected error creating debug information file 'C:\DevProjects\Allstar
Admin\Allstar.Common.DataAccess\obj\Debug\Allstar. Common.DataAccess.PDB' --
'C:\DevProjects\Allstar
Admin\Allstar.Common.DataAccess\obj\Debug\Allstar. Common.DataAccess.pdb: The
process cannot access the file because it is being used by another process.
'

If I exit Visual Studio and delete the obj directory under the DLL giving me
problems and they reload VS it works fine, but this is not a very good
solution.

I have read posts that say to change to Release from Debug and back but that
is only temporary too and does not always work.

Obviously DEVENV.EXE has ahold of my DLL. Any ideas how to fix this with
compiler settings or code changes to be aware of?

I have also read to not have Enums inside my class, I did, and moved them to
just inside the namespace but that did not help either.

Finally, my project consists of a few User Controls which use this DLL. I
cannot determine when the error starts, I may do a build 10 times with no
problem but number 11 will be the problem, other times it takes 5 builds.

Thank you in advance,
Rob Bazinet

Jul 22 '05 #1
6 3986
> If I exit Visual Studio and delete the obj directory under the DLL giving me
problems and they reload VS it works fine, but this is not a very good
solution. If you exit VS and restart without deleting the obj directory, does it work?

Since VS.NET is locking the Assembly, restarting should fix the issue without deleting the directory.

Try setting "CopyLocal" to true in the property grid on the assembly reference, if it is not already.

This will provide a copy of the referenced Assembly to VS.NET so that it can lock it for intellisense (which is what the cause of
your problem is, most likely).

--
Dave Sexton
dave@www..jwaonline..com
-----------------------------------------------------------------------
"rbazinet" <rb******@discussions.microsoft.com> wrote in message news:B5**********************************@microsof t.com...I have a VS 2003 C# project, web app with a bunch of DLL's. When I compile
my project I often times get this message:

Unexpected error creating debug information file 'C:\DevProjects\Allstar
Admin\Allstar.Common.DataAccess\obj\Debug\Allstar. Common.DataAccess.PDB' --
'C:\DevProjects\Allstar
Admin\Allstar.Common.DataAccess\obj\Debug\Allstar. Common.DataAccess.pdb: The
process cannot access the file because it is being used by another process.
'

If I exit Visual Studio and delete the obj directory under the DLL giving me
problems and they reload VS it works fine, but this is not a very good
solution.

I have read posts that say to change to Release from Debug and back but that
is only temporary too and does not always work.

Obviously DEVENV.EXE has ahold of my DLL. Any ideas how to fix this with
compiler settings or code changes to be aware of?

I have also read to not have Enums inside my class, I did, and moved them to
just inside the namespace but that did not help either.

Finally, my project consists of a few User Controls which use this DLL. I
cannot determine when the error starts, I may do a build 10 times with no
problem but number 11 will be the problem, other times it takes 5 builds.

Thank you in advance,
Rob Bazinet

Jul 22 '05 #2
Dave,

Thanks for the reply.

Yes, if I exit VS and go back in I do not have to delete the obj directory.
I am looking for a solution to my problem that can keep me in VS without
having to exit.

All of my DLL references for DLL are set to CopyLocal=true. Since I have a
bunch of other DLL's and this is not happening then it must be something
different about this DLL and this is the guidance I am looking for.

If I do a Google search on this problem I see it all over the place but no
real answers except exiting VS, which is not a solution.

-Rob
"Dave" wrote:
If I exit Visual Studio and delete the obj directory under the DLL giving me
problems and they reload VS it works fine, but this is not a very good
solution.

If you exit VS and restart without deleting the obj directory, does it work?

Since VS.NET is locking the Assembly, restarting should fix the issue without deleting the directory.

Try setting "CopyLocal" to true in the property grid on the assembly reference, if it is not already.

This will provide a copy of the referenced Assembly to VS.NET so that it can lock it for intellisense (which is what the cause of
your problem is, most likely).

--
Dave Sexton
dave@www..jwaonline..com
-----------------------------------------------------------------------
"rbazinet" <rb******@discussions.microsoft.com> wrote in message news:B5**********************************@microsof t.com...
I have a VS 2003 C# project, web app with a bunch of DLL's. When I compile
my project I often times get this message:

Unexpected error creating debug information file 'C:\DevProjects\Allstar
Admin\Allstar.Common.DataAccess\obj\Debug\Allstar. Common.DataAccess.PDB' --
'C:\DevProjects\Allstar
Admin\Allstar.Common.DataAccess\obj\Debug\Allstar. Common.DataAccess.pdb: The
process cannot access the file because it is being used by another process.
'

If I exit Visual Studio and delete the obj directory under the DLL giving me
problems and they reload VS it works fine, but this is not a very good
solution.

I have read posts that say to change to Release from Debug and back but that
is only temporary too and does not always work.

Obviously DEVENV.EXE has ahold of my DLL. Any ideas how to fix this with
compiler settings or code changes to be aware of?

I have also read to not have Enums inside my class, I did, and moved them to
just inside the namespace but that did not help either.

Finally, my project consists of a few User Controls which use this DLL. I
cannot determine when the error starts, I may do a build 10 times with no
problem but number 11 will be the problem, other times it takes 5 builds.

Thank you in advance,
Rob Bazinet


Jul 22 '05 #3
This is where I found my information, but I couldn't find anything about your particular "debug file" issue other than in the
compiler documentation and that didn't add anything useful:

http://support.microsoft.com/default...b;en-us;313512

Maybe VS.net is locking your debug file when it loads your UserControls into the toolbox, but other than that I see no reason for
VS.net to even need the .pdb file.

Sorry I couldn't help more.

--
Dave Sexton
dave@www..jwaonline..com
-----------------------------------------------------------------------
"rbazinet" <rb******@discussions.microsoft.com> wrote in message news:8D**********************************@microsof t.com...
Dave,

Thanks for the reply.

Yes, if I exit VS and go back in I do not have to delete the obj directory.
I am looking for a solution to my problem that can keep me in VS without
having to exit.

All of my DLL references for DLL are set to CopyLocal=true. Since I have a
bunch of other DLL's and this is not happening then it must be something
different about this DLL and this is the guidance I am looking for.

If I do a Google search on this problem I see it all over the place but no
real answers except exiting VS, which is not a solution.

-Rob
"Dave" wrote:
> If I exit Visual Studio and delete the obj directory under the DLL giving me
> problems and they reload VS it works fine, but this is not a very good
> solution.

If you exit VS and restart without deleting the obj directory, does it work?

Since VS.NET is locking the Assembly, restarting should fix the issue without deleting the directory.

Try setting "CopyLocal" to true in the property grid on the assembly reference, if it is not already.

This will provide a copy of the referenced Assembly to VS.NET so that it can lock it for intellisense (which is what the cause of
your problem is, most likely).

--
Dave Sexton
dave@www..jwaonline..com
-----------------------------------------------------------------------
"rbazinet" <rb******@discussions.microsoft.com> wrote in message news:B5**********************************@microsof t.com...
>I have a VS 2003 C# project, web app with a bunch of DLL's. When I compile
> my project I often times get this message:
>
> Unexpected error creating debug information file 'C:\DevProjects\Allstar
> Admin\Allstar.Common.DataAccess\obj\Debug\Allstar. Common.DataAccess.PDB' --
> 'C:\DevProjects\Allstar
> Admin\Allstar.Common.DataAccess\obj\Debug\Allstar. Common.DataAccess.pdb: The
> process cannot access the file because it is being used by another process.
> '
>
> If I exit Visual Studio and delete the obj directory under the DLL giving me
> problems and they reload VS it works fine, but this is not a very good
> solution.
>
> I have read posts that say to change to Release from Debug and back but that
> is only temporary too and does not always work.
>
> Obviously DEVENV.EXE has ahold of my DLL. Any ideas how to fix this with
> compiler settings or code changes to be aware of?
>
> I have also read to not have Enums inside my class, I did, and moved them to
> just inside the namespace but that did not help either.
>
> Finally, my project consists of a few User Controls which use this DLL. I
> cannot determine when the error starts, I may do a build 10 times with no
> problem but number 11 will be the problem, other times it takes 5 builds.
>
> Thank you in advance,
> Rob Bazinet
>


Jul 22 '05 #4
I just read about the same issue in Frans Boumas blog:

http://weblogs.asp.net/fbouma/archive/2005/07/13.aspx

There is a link in the blog to an MSDN KB article. Apparently there is a
fix, but you have to request it.

HTH
Dan

"rbazinet" wrote:
I have a VS 2003 C# project, web app with a bunch of DLL's. When I compile
my project I often times get this message:

Unexpected error creating debug information file 'C:\DevProjects\Allstar
Admin\Allstar.Common.DataAccess\obj\Debug\Allstar. Common.DataAccess.PDB' --
'C:\DevProjects\Allstar
Admin\Allstar.Common.DataAccess\obj\Debug\Allstar. Common.DataAccess.pdb: The
process cannot access the file because it is being used by another process.
'

If I exit Visual Studio and delete the obj directory under the DLL giving me
problems and they reload VS it works fine, but this is not a very good
solution.

I have read posts that say to change to Release from Debug and back but that
is only temporary too and does not always work.

Obviously DEVENV.EXE has ahold of my DLL. Any ideas how to fix this with
compiler settings or code changes to be aware of?

I have also read to not have Enums inside my class, I did, and moved them to
just inside the namespace but that did not help either.

Finally, my project consists of a few User Controls which use this DLL. I
cannot determine when the error starts, I may do a build 10 times with no
problem but number 11 will be the problem, other times it takes 5 builds.

Thank you in advance,
Rob Bazinet

Jul 22 '05 #5
Dan,

Thank you for the post. It's interesting to see it is such a widespread
issue with a solution that is not publicly available. I called Microsoft and
requested the fix, I have installed it and all seems good so far.

FWIW, the tech I spoke with on the C# Support Team said a service pack for
VS.NET 2003 is expected in August/September timeframe.

-Rob
"Dan Kelley" wrote:
I just read about the same issue in Frans Boumas blog:

http://weblogs.asp.net/fbouma/archive/2005/07/13.aspx

There is a link in the blog to an MSDN KB article. Apparently there is a
fix, but you have to request it.

HTH
Dan

"rbazinet" wrote:
I have a VS 2003 C# project, web app with a bunch of DLL's. When I compile
my project I often times get this message:

Unexpected error creating debug information file 'C:\DevProjects\Allstar
Admin\Allstar.Common.DataAccess\obj\Debug\Allstar. Common.DataAccess.PDB' --
'C:\DevProjects\Allstar
Admin\Allstar.Common.DataAccess\obj\Debug\Allstar. Common.DataAccess.pdb: The
process cannot access the file because it is being used by another process.
'

If I exit Visual Studio and delete the obj directory under the DLL giving me
problems and they reload VS it works fine, but this is not a very good
solution.

I have read posts that say to change to Release from Debug and back but that
is only temporary too and does not always work.

Obviously DEVENV.EXE has ahold of my DLL. Any ideas how to fix this with
compiler settings or code changes to be aware of?

I have also read to not have Enums inside my class, I did, and moved them to
just inside the namespace but that did not help either.

Finally, my project consists of a few User Controls which use this DLL. I
cannot determine when the error starts, I may do a build 10 times with no
problem but number 11 will be the problem, other times it takes 5 builds.

Thank you in advance,
Rob Bazinet

Jul 22 '05 #6
Dave,

Your help is much appreciated. If you look at Dan Kelley's post on this
thread you can see a link to somone else who has the problem and the fix. It
seems MS has a hotfix for this problem that is available by request.

Thanks,
Rob
"Dave" wrote:
This is where I found my information, but I couldn't find anything about your particular "debug file" issue other than in the
compiler documentation and that didn't add anything useful:

http://support.microsoft.com/default...b;en-us;313512

Maybe VS.net is locking your debug file when it loads your UserControls into the toolbox, but other than that I see no reason for
VS.net to even need the .pdb file.

Sorry I couldn't help more.

--
Dave Sexton
dave@www..jwaonline..com
-----------------------------------------------------------------------
"rbazinet" <rb******@discussions.microsoft.com> wrote in message news:8D**********************************@microsof t.com...
Dave,

Thanks for the reply.

Yes, if I exit VS and go back in I do not have to delete the obj directory.
I am looking for a solution to my problem that can keep me in VS without
having to exit.

All of my DLL references for DLL are set to CopyLocal=true. Since I have a
bunch of other DLL's and this is not happening then it must be something
different about this DLL and this is the guidance I am looking for.

If I do a Google search on this problem I see it all over the place but no
real answers except exiting VS, which is not a solution.

-Rob
"Dave" wrote:
> If I exit Visual Studio and delete the obj directory under the DLL giving me
> problems and they reload VS it works fine, but this is not a very good
> solution.
If you exit VS and restart without deleting the obj directory, does it work?

Since VS.NET is locking the Assembly, restarting should fix the issue without deleting the directory.

Try setting "CopyLocal" to true in the property grid on the assembly reference, if it is not already.

This will provide a copy of the referenced Assembly to VS.NET so that it can lock it for intellisense (which is what the cause of
your problem is, most likely).

--
Dave Sexton
dave@www..jwaonline..com
-----------------------------------------------------------------------
"rbazinet" <rb******@discussions.microsoft.com> wrote in message news:B5**********************************@microsof t.com...
>I have a VS 2003 C# project, web app with a bunch of DLL's. When I compile
> my project I often times get this message:
>
> Unexpected error creating debug information file 'C:\DevProjects\Allstar
> Admin\Allstar.Common.DataAccess\obj\Debug\Allstar. Common.DataAccess.PDB' --
> 'C:\DevProjects\Allstar
> Admin\Allstar.Common.DataAccess\obj\Debug\Allstar. Common.DataAccess.pdb: The
> process cannot access the file because it is being used by another process.
> '
>
> If I exit Visual Studio and delete the obj directory under the DLL giving me
> problems and they reload VS it works fine, but this is not a very good
> solution.
>
> I have read posts that say to change to Release from Debug and back but that
> is only temporary too and does not always work.
>
> Obviously DEVENV.EXE has ahold of my DLL. Any ideas how to fix this with
> compiler settings or code changes to be aware of?
>
> I have also read to not have Enums inside my class, I did, and moved them to
> just inside the namespace but that did not help either.
>
> Finally, my project consists of a few User Controls which use this DLL. I
> cannot determine when the error starts, I may do a build 10 times with no
> problem but number 11 will be the problem, other times it takes 5 builds.
>
> Thank you in advance,
> Rob Bazinet
>


Jul 22 '05 #7

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

4
by: Alan Little | last post by:
This is very bizarre. Could someone else have a look at this? Maybe you can see something I'm overlooking. Go here: http://www.newsletters.forbes.com/enews/admin/deliver.php4 U: bugtest P:...
22
by: Elbert Lev | last post by:
# here is the problem I ran into: class foo: def __init__(self, host): self.f() self.r = True def f(self): if self.r: #<do something>
2
by: Teddy | last post by:
Hello all I've just upgraded my g++ compiler to 3.3.3 on Cygwin. But there is always a annoying warnig message "no new line at end of file" no matter what code you writes. How to get rid of...
6
by: rbazinet | last post by:
I have a VS 2003 C# project, web app with a bunch of DLL's. When I compile my project I often times get this message: Unexpected error creating debug information file 'C:\DevProjects\Allstar...
52
by: Michael Hopkins | last post by:
Hi all We all know that C++ is a cleverly conceived multi-paradigm language that sacrifices very little in efficiency for what it delivers in terms of type-safety, encapsulation and generic...
4
by: Neo Geshel | last post by:
Just moved to C# from VB.NET, frustrated to hell and back by inability to get much-copied (from about 20+ different resources) literal example to work. Master Page content: <meta...
0
by: ckfan.painter | last post by:
I've run into a seemingly bizarre problem with insert() for std::vector. (This was done on Microsoft Visual C++ 2005 express version 8...maybe it is a compiler specific bug?) Here's the code: ...
3
by: Don Miller | last post by:
I have a bizarre problem when I try to validate XML documents and their schemas once they have been opened and transfered to a Visual Web Developer 2005 Express project. I receive validation errors...
6
by: =?Utf-8?B?QWxhbiBXaWxsaWFtcy1LZXk=?= | last post by:
I am being bugged by some bizarre compiler errors when compiling in debug configuration (but not in release). Here is a test function... void test() { int i = 1; ASSERT(i==0); } When I...
1
by: CloudSolutions | last post by:
Introduction: For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
0
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome former...
0
by: ryjfgjl | last post by:
In our work, we often need to import Excel data into databases (such as MySQL, SQL Server, Oracle) for data analysis and processing. Usually, we use database tools like Navicat or the Excel import...
0
by: taylorcarr | last post by:
A Canon printer is a smart device known for being advanced, efficient, and reliable. It is designed for home, office, and hybrid workspace use and can also be used for a variety of purposes. However,...
0
by: Charles Arthur | last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
0
by: aa123db | last post by:
Variable and constants Use var or let for variables and const fror constants. Var foo ='bar'; Let foo ='bar';const baz ='bar'; Functions function $name$ ($parameters$) { } ...
0
by: ryjfgjl | last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
1
by: nemocccc | last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
0
by: Hystou | last post by:
There are some requirements for setting up RAID: 1. The motherboard and BIOS support RAID configuration. 2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.