Re: VS2005 mixed project intellisense confusion

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

No idea or suggestion but my advice always is to keep the two project
separate and not in the same solution. I don't even have both projects open
at the same time. This avoids corner case issues like the ones you are
facing and also plays better with source control.

Cheers
Daniel
--
http://www.danielmoth.com/Blog/

"tb2000" <tb2000@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:06FEFAC0-D20C-41A4-8185-EAE9D4169CF1@xxxxxxxxxxxxxxxx
My scenario:

- VS2005
- mixed projects (smart device and desktop) in a single sln
- a single source-tree for all projects.
- the primary project directly references the source files,
- the other projects use reference-links (to the source files).

Now various observations I could not find yet how to control:

- during a compile run there is errors (ok, that happens :-) ) and the
files
which VS then actually opens apparently are referenced from the direct
references, not via the links: This leads to intellisense confusion
because
intellisense now interprets the files with the #if constants as defined in
the primary project and not the project which is currently being compiled
(regardless if set as ActiveProject or not btw).

- the same applies to files opened when a breaqkpoint is being hit.

- to make things worse: sometimes the IDE seems to get confused that if a
file is actually displayed in the editor (possibly from the before
explained
wrong selection) the next compile run for the active project (or any
actually
except the primary) fails as the IDE compiled the respective module with
the
settings not belonging to neither the active nor the compiled project but
with the settings the IDE takes from the falsely associated project.

Any idea or suggestion where (if possible) to affect that strange
behavior?

Thankx ahead!

tb

PS: this is probably relevant for vstudio.general, so I'll try to
crosspost,
not sur e if that is the correct url: vstudio.general


.

Relevant Pages

  • Re: Error loading Global
    ... Look at the assemblies referenced in the IDE. ... you have more references already coded into the compiler, ... I would think that it would blow up on compile, ... Compile with warnings as errors and fix all warnings prior to ...
    (microsoft.public.dotnet.faqs)
  • Re: Error loading Global
    ... Look at the assemblies referenced in the IDE. ... you have more references already coded into the compiler, ... I would think that it would blow up on compile, ... Compile with warnings as errors and fix all warnings prior to ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Error loading Global
    ... Look at the assemblies referenced in the IDE. ... you have more references already coded into the compiler, ... I would think that it would blow up on compile, ... Compile with warnings as errors and fix all warnings prior to ...
    (microsoft.public.dotnet.framework.aspnet)
  • VB.NET 2002 IDE Failing to update local dependencies
    ... Standard IDE. ... assembly *should* update its references to any new version, ... compile. ... I've now started including an assemblyVersion property to all ...
    (microsoft.public.dotnet.languages.vb)
  • Re: translation functions
    ... The Compile option turning gray is normal: ... Doug Steele, Microsoft Access MVP ... None of the references are missing ... then go back in and unselect the reference you just added. ...
    (microsoft.public.access.gettingstarted)