Why VS 2010 sucks today
-
And VS2008 as far as I can remember, and perhaps earlier versions too. If I have two C++ projects, ProjectA which produces a static library and ProjectB hat uses that lib, after building ProjectB for the first time Visual Studio will keep the ProjectA.lib file locked, so that any subsequent builds will fail because it can't update or access ProjectA.lib so you have to restart Visual Studio to build the project again. This happens every time, and it's starting to become a little tedious.
My current favourite phrase: I've seen better!
-SK Genius
We ran into this with 2005 and 2008. What we did to get around it was to add a post build step to copy the lib to a different folder and then in the second project it referenced that one instead of the one that was built directly. Definately a PITA, but it worked for us.
Steve Maier
-
And VS2008 as far as I can remember, and perhaps earlier versions too. If I have two C++ projects, ProjectA which produces a static library and ProjectB hat uses that lib, after building ProjectB for the first time Visual Studio will keep the ProjectA.lib file locked, so that any subsequent builds will fail because it can't update or access ProjectA.lib so you have to restart Visual Studio to build the project again. This happens every time, and it's starting to become a little tedious.
My current favourite phrase: I've seen better!
-SK Genius
I've not experienced this oddity at all. With either Static libs or Dynamic ones. Are you sure that the lock is from VS? :)
Chris Meech I am Canadian. [heard in a local bar] In theory there is no difference between theory and practice. In practice there is. [Yogi Berra] posting about Crystal Reports here is like discussing gay marriage on a catholic church’s website.[Nishant Sivakumar]
-
We ran into this with 2005 and 2008. What we did to get around it was to add a post build step to copy the lib to a different folder and then in the second project it referenced that one instead of the one that was built directly. Definately a PITA, but it worked for us.
Steve Maier
Interesting workaround. Take a 5 for the tip.
Regards, Nish
My technology blog: voidnish.wordpress.com
-
I've not experienced this oddity at all. With either Static libs or Dynamic ones. Are you sure that the lock is from VS? :)
Chris Meech I am Canadian. [heard in a local bar] In theory there is no difference between theory and practice. In practice there is. [Yogi Berra] posting about Crystal Reports here is like discussing gay marriage on a catholic church’s website.[Nishant Sivakumar]
Well, restarting VS always fixed it... easy way to check though *goes and looks* EDIT: Yup, devenv.exe has the file.
My current favourite phrase: I've seen better!
-SK Genius
Source Indexing and Symbol Servers[^]
modified on Wednesday, January 19, 2011 12:53 PM
-
And VS2008 as far as I can remember, and perhaps earlier versions too. If I have two C++ projects, ProjectA which produces a static library and ProjectB hat uses that lib, after building ProjectB for the first time Visual Studio will keep the ProjectA.lib file locked, so that any subsequent builds will fail because it can't update or access ProjectA.lib so you have to restart Visual Studio to build the project again. This happens every time, and it's starting to become a little tedious.
My current favourite phrase: I've seen better!
-SK Genius
-
We ran into this with 2005 and 2008. What we did to get around it was to add a post build step to copy the lib to a different folder and then in the second project it referenced that one instead of the one that was built directly. Definately a PITA, but it worked for us.
Steve Maier
An excellent idea, I was trying to use the project dependencies and "Link with project dependencies" option, but if it means I don't have to restart visual studio every time I want to do a build then then I guess it's the only way to go.
My current favourite phrase: I've seen better!
-SK Genius
-
And VS2008 as far as I can remember, and perhaps earlier versions too. If I have two C++ projects, ProjectA which produces a static library and ProjectB hat uses that lib, after building ProjectB for the first time Visual Studio will keep the ProjectA.lib file locked, so that any subsequent builds will fail because it can't update or access ProjectA.lib so you have to restart Visual Studio to build the project again. This happens every time, and it's starting to become a little tedious.
My current favourite phrase: I've seen better!
-SK Genius
-
Is this in the same solution? If it is with two instances open for two solutions then I'm not surprised.
Join the cool kids - Come fold with us[^]
Nope, same solution. With project dependencies and Link Library Dependencies set.
My current favourite phrase: I've seen better!
-SK Genius
-
And VS2008 as far as I can remember, and perhaps earlier versions too. If I have two C++ projects, ProjectA which produces a static library and ProjectB hat uses that lib, after building ProjectB for the first time Visual Studio will keep the ProjectA.lib file locked, so that any subsequent builds will fail because it can't update or access ProjectA.lib so you have to restart Visual Studio to build the project again. This happens every time, and it's starting to become a little tedious.
My current favourite phrase: I've seen better!
-SK Genius
Have you reported to Microsoft Connect[^]?
FILETIME to time_t
| FoldWithUs! | sighist | WhoIncludes - Analyzing C++ include file hierarchy -
And VS2008 as far as I can remember, and perhaps earlier versions too. If I have two C++ projects, ProjectA which produces a static library and ProjectB hat uses that lib, after building ProjectB for the first time Visual Studio will keep the ProjectA.lib file locked, so that any subsequent builds will fail because it can't update or access ProjectA.lib so you have to restart Visual Studio to build the project again. This happens every time, and it's starting to become a little tedious.
My current favourite phrase: I've seen better!
-SK Genius
There is a known problem that sometimes happens when a designer is open it locks a file and build fails. Have you got a designer open? Work around from MS...close all designers.
I like long walks, especially when they are taken by people who annoy me. http://www.hq4thmarinescomm.com[^]
My Site -
There is a known problem that sometimes happens when a designer is open it locks a file and build fails. Have you got a designer open? Work around from MS...close all designers.
I like long walks, especially when they are taken by people who annoy me. http://www.hq4thmarinescomm.com[^]
My SiteNo designers in site, It's basically only a static library and a console app to run a couple of tests on. It's all a bit weird. It has (seemed to, for now) stopped doing it since I went through the project dependencies and References and enabled / disabled linking with dependencies and the dependencies themselves.
My current favourite phrase: I've seen better!
-SK Genius
-
No designers in site, It's basically only a static library and a console app to run a couple of tests on. It's all a bit weird. It has (seemed to, for now) stopped doing it since I went through the project dependencies and References and enabled / disabled linking with dependencies and the dependencies themselves.
My current favourite phrase: I've seen better!
-SK Genius
The beast with a mind of it's own for sure. I'm currently working in VS2008 and the properties color picker decided it would go to just giving me a list of colors instead of the ever so faithful {custom, web, system } had to restart VS to get regular color picker back.
I like long walks, especially when they are taken by people who annoy me. http://www.hq4thmarinescomm.com[^]
My Site -
We ran into this with 2005 and 2008. What we did to get around it was to add a post build step to copy the lib to a different folder and then in the second project it referenced that one instead of the one that was built directly. Definately a PITA, but it worked for us.
Steve Maier
