I have been having problems with Visual Studio. I am running a solution file that has 20 projects. When I try to debug the web project in my solution, I often get an error about a missing assembly. Once I get this error, I have to at least shut down and restart Visual Studio, and often I have to restart my computer to resolve the issue. I did some research and found that there is a known error in Visual Studio when you have both project references and file references in your solution. There is a hot fix, but you have to call Microsoft to get it, and the hot fix sounds pretty unstable.
Has anyone else come across a similar problem? Has anyone installed the hot fix? Has anyone fixed this issue by getting rid of the solution file and only using file references?
Subscribe to:
Post Comments (Atom)
4 comments:
Why do you say the hot fix sounds unstable? Are people complaining about it in the newsgroups?
I personally don't have any experience with this particular problem, sorry.
This line made me question whether I should install the hot fix:
"This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Visual Studio .NET 2003 service pack that contains this hotfix."
That quote worries me. I am not sure if I am "severely" affected.
I think that is the same wording they use for all hot fixes. Since the fix hasn't been through Microsoft's complete regression test suite, it makes sense for them to try to limit the number of users who have access to the fix.
If it were me, I'd try to solve the problem by switching to file references before I'd try the hot fix, in part because it will take a while to get the hot fix anyway.
We have a similar problem in our project.
DataLayer
BusinessLayer
ClientLayer
all three separate projects in a solution, which correct build order, project references, and dlls.
When we make changes to all 3 layers specifically the data and business layer together, Visual Studio compiler doesn't see the additions or changes until we close Visual Studio and open it back up. It won't even compile, says that the type or method does not exist.
The line that comes back in the compiler says something to the fact that it can't copy the dll. strange.
Jake
Jake
from whoISjake.com fame
Post a Comment