I've got a 33 project solution, with many of the projects being decent size 30-40 forms I suppose. I had originally went with a single solution model, but the performance was very poor. So I switched everything around to use a single solution per project and replaced project references with references to a common build directory.
However, this means that I sacrifice some of the benefits of being able to refactor. I'd like to be able to refactor some public API's and let the IDE handle updating the required references.
What I have been thinking about doing is writing something (probably stick it into an MSBuild task) that will dynamically generate a solution file for a given project (the one I want to refactor) and include all the projects that reference it in the solution. The difficulty arises because the refactoring engine doesn't recognize to update the other projects that are referenced via the common build output folder, so I'm guessing I need to use project references in this case. So, I'm looking for a solution, maybe a way to conditionally tell the project file to use project references vs my common path.
Thanks
Visual Basic Large Projects/Solutions
Carlton Lane
HackMax
Hi Chris,
To help us investigate, can you answer some follow-up questions on the perf issues you're experiencing You can reply to me directly in mail: pdarragh*at*microsoft.com.
1. Are your projects all in VB or are you using other languages
2. Can you roughly outline the dependency tree of the components in your solution
3. Did you migrate your project from VS2003 Did you have pre-RTM bits of VS 2005 installed on your machine
4. How big is the VB code file that is taking 10sec to open
5. Specifically what actions do you find slow in the code editor (intellisense, typing, etc) Are you finding any perf issues with debugging
6. What is the machine config (RAM, CPU)
Thanks,
-Patrick Darragh
VB PM
TonyKing
Opening of the solution is slow, but not unreasonable.
When working in the code window it feels like I'm using remote desktop over a slow connection. Many of these are winforms projects, but I'm rarely in the forms designer. Builds were also rather slow because it seemed like regardless of changes the .resx files were always processed.
The solution explorer window is also sluggish, expanding / collapsing projects. Double clicking on a VB file to open will takes sometimes 10 seconds.
Mike C
Hi, thanks for your feedback. In the upcoming versions of Visual Studio we are looking to improve performance and scalability with respect to large projects/solutions, but to do that most effectively, we need detailed feedback from users on where the performance bottlenecks are.
Could you elaborate more on what the performance issues were with a single solution model For example, what seemed to be slow Opening of the solution Working with code files/designers Something else
Thanks!
-- Izzy
Izzy Gryko
Lead Software Design Engineer
Visual Studio Core Development
izzyg@microsoft.com