By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
449,277 Members | 1,244 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 449,277 IT Pros & Developers. It's quick & easy.

Compile errors in VS.Net 2003 - VB.Net solution

P: n/a
Hi,

We are using VS.Net 2003 and coding in VB.net. The
solution has 38 projects; most of the projects in the
solution reference other projects (without any circular
references) and all the references were added to using the
Projects tab on the Add Reference dialog and not by
browsing to the DLL for the project.

When we build or run the solution "bogus" compile errors
show up for classes in projects that were not modified
before building the solution and in most cases are not
even open in the IDE at the time. The compile errors
typically say that a data member is missing or a control
is missing from the class and they will only go away, if
we rebuild the solution or just close and open it again.
Sometimes even while rebuilding other compile errors
related to .resources files not being accessible show up
and then we have to delete the bin and Debug folders for
the project containing the class and only then rebuild
works.

We have had this problem for some time now but it was NOT
as frequent (we saw them once or twice every week), lately
it has been happening almost every time we try to compile
the solution after making a change.

Any ideas what could be causing this? Would rebuilding the
solution by removing all the projects from it and adding
those back help?

Thanks in advance

Ravi

Nov 21 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Hi Ravi,

I tried to repro this with a multi project solution with several references, but I couldn't. In the cases where you get the build errors, does the project with the
build errors always reference a project that has been changed? It may be that the work around is to change the order of when the projects in the solution
are compiled (but I'm just guessing).

Craig VB.Net Team
--------------------------------------------------------------------
This reply is provided AS IS, without warranty (express or implied).
--------------------
Content-Class: urn:content-classes:message
From: "Ravi Chaudhary" <an*******@discussions.microsoft.com>
Sender: "Ravi Chaudhary" <an*******@discussions.microsoft.com>
Subject: Compile errors in VS.Net 2003 - VB.Net solution
Date: Tue, 31 Aug 2004 10:04:06 -0700
Lines: 35
Message-ID: <00****************************@phx.gbl>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Thread-Index: AcSPfIY9kqhBR5/+QqCiLSR/LAh9cQ==
Newsgroups: microsoft.public.dotnet.languages.vb
Path: cpmsftngxa10.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.dotnet.languages.vb:226651
NNTP-Posting-Host: tk2msftngxa12.phx.gbl 10.40.1.164
X-Tomcat-NG: microsoft.public.dotnet.languages.vb

Hi,

We are using VS.Net 2003 and coding in VB.net. The
solution has 38 projects; most of the projects in the
solution reference other projects (without any circular
references) and all the references were added to using the
Projects tab on the Add Reference dialog and not by
browsing to the DLL for the project.

When we build or run the solution "bogus" compile errors
show up for classes in projects that were not modified
before building the solution and in most cases are not
even open in the IDE at the time. The compile errors
typically say that a data member is missing or a control
is missing from the class and they will only go away, if
we rebuild the solution or just close and open it again.
Sometimes even while rebuilding other compile errors
related to .resources files not being accessible show up
and then we have to delete the bin and Debug folders for
the project containing the class and only then rebuild
works.

We have had this problem for some time now but it was NOT
as frequent (we saw them once or twice every week), lately
it has been happening almost every time we try to compile
the solution after making a change.

Any ideas what could be causing this? Would rebuilding the
solution by removing all the projects from it and adding
those back help?

Thanks in advance

Ravi


Thanks & Regards
Santhosh Somayajulu
Internet Information Services Team,
Microsoft
Nov 21 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.