This VC# bug is killing me - please help somebody!
-
I am currently working on a .NET project with over 40 projects in the solution and due to the dependencies each developer needs access/reference to at least 3 assemblies (most of them over 80 KB). To make other tools, testing, documentations, sample codes etc easier to handle, I had to build all this project to a common output and this VC# bug - Q313512[^], is killing me. I requested the guy in charge of the my company's MSDN subscription to enquire for hotfix (QFE), but MS is claiming we had to pay an equivalent of $350 just to enquire the presense of a hotfix, a so-called support instance. We sent an email. My company is not willing to pay this amount and I had to suffer for an acknowleged bug - closing my solutions and then re-opening each time to effect a rebuild. Please help. How are you guys using this VS.NET productively? (to me it is more of a headache than a solution) :(( Best regards, Paul. Jesus Christ is LOVE! Please tell somebody.
So long as MS acknowledges that the problem is due to a bug (given that it has published the KB article, this just means you need to convince them that you have encountered the situation described there) you will get a refund. If you pay for it as a one-off then I don't know whether you get the money back or whether you get the next support call free.
-
:sigh: You misread my entire post! :doh: Let's go: 1. You have some DLLs that need to be on specific directories after the build of a project, but before the build of another. You can't generate them on those directories because of a VS.NET bug. What do you do? Generate on a temporary directory and move them. 2. You said people do not need to recompile them often; move them to another solution, and build them manually. Paul Selormey wrote: This bug has nothing to do with 178 projects-solution. You only need an assembly which is more than 60 KB to get into this problem. You can work on 2000 projects, if none is more than 60 KB you do not have the problem. No, this bug has to do with poor planning on the build process: if you're referencing projects, your solution should contain projects that generate DLLs. If you're referencing DLLs, your solution should contain those DLLs. Sorry, I can't explain it simpler than that. Due to technical difficulties my previous signature, "I see dumb people" will be off until further notice. Too many people were thinking I was talking about them... :sigh:
I have experienced the exact same problem with assemblies getting larger than 60KB. Very crappy.
-
Doesn't matter anyway... I have a (large) solution with all binaries outputting to the correct folders and Copy Local set correctly etc etc and all the other conditions being correct I STILL get the error occasionally... ----------------------------------------------------------------------- Shaun Austin: .NET Specialist. Spreading the word of .NET to the world... well the UK... well my tiny corner of it!! :-D
Not quite sure why that last comment deserved a "1" vote... it's just a statement of fact! ----------------------------------------------------------------------- Shaun Austin: .NET Specialist. Spreading the word of .NET to the world... well the UK... well my tiny corner of it!! :-D