Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Another Unexpected Error
Message
De
21/04/2004 10:51:42
 
 
À
21/04/2004 10:38:40
Information générale
Forum:
ASP.NET
Catégorie:
Autre
Divers
Thread ID:
00896830
Message ID:
00896903
Vues:
28
Kevin,

>After having to rebuild my solution from scratch for the third time this year, I've scrapped my solution. I seem to encounter less issues if I avoid building a solution and just work with projects individually (which I think was what Bonnie was saying).

Hmmm ... nope, not quite what I was saying. I was only saying to compile the one project individually that was giving him problems ... sometimes that will fix it. When you're developing, how can you avoid rebuilding the entire solution when you need to test the application? How do you test individual projects (.DLLs) without having something to run them? I guess I don't quite see what you mean.

>I've also seen situations in a solution where VS.NET winds up pointing to the wrong place for a DLL reference. Again, if I build projects individually, many problems seem to go away.

Have you checked the Configuration Manager? <s>

I've observed just the opposite behavior than you have Kevin ... VS2003 definitely seems to be less buggy to me than 2002 was and there seems to be less "confusion". I wonder maybe if it depends somewhat on the types of applications we're developing? I dunno ...

~~Bonnie

>Bonnie/JB...
>
>Actually, my (unofficial) observation is that VS2003's behavior in this area is as bad or worse than the original version. I realize VS2003 took care of many issues, so I'm not suggesting going back, but my own experience is that compiler/solution 'confusion' is worse in VS2003.
>
>After having to rebuild my solution from scratch for the third time this year, I've scrapped my solution. I seem to encounter less issues if I avoid building a solution and just work with projects individually (which I think was what Bonnie was saying).
>
>I can easily reproduce issues where certain third-party DLLs don't work well when specified as references in any type of complex solution file.
>
>I've also seen situations in a solution where VS.NET winds up pointing to the wrong place for a DLL reference. Again, if I build projects individually, many problems seem to go away.
>
>Kevin
Bonnie Berent DeWitt
NET/C# MVP since 2003

http://geek-goddess-bonnie.blogspot.com
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform