If you only have a single project, the solution will not show hence you can't see the Configuration Manager. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?
Collectives on Stack Overflow. Learn more. Asked 12 years, 1 month ago. Active 7 years, 7 months ago. Viewed 24k times. How do I get the Configuration Manager to work for all projects? Improve this question. Add a comment. So there are two build configs per client. This wasn't a problem with just a few different client versions but now we have 23 clients. Otherwise this has worked quite well but the increasing number of clients has made the build configuration management a real pain.
Any alternate solutions for this since I'm clearly looking the whole problem from a completely wrong angle and turned this in a major WTF.
From a configuration standpoint, it sounds like the classic "Pre-Build Plugin Architecture" problem; you have a baseline application and a "Plugin" is applied css, resource dlls, etc applied "in house" before deployment "to the field. What's unclear is whether a baseline update triggers all clients to be updated, or if they are updated on an as-needed basis. Tossing in staging deployments makes matters even more tricky, since your testing level currently, only Staging it seems is a multiplier of complexity.
The first step is to re-evaluate your build process to remove duplication. You don't need two build configs per client; figure out a way to programmatically modify project files when your build runs so CruiseControl will be happy. Next, try to isolate the plugins from the baseline application. Think of each plug-in as a micro-app in and of itself, not as an integral part of your basline application. Reason being It'd be a great problem to have, but whooooa momma would it be a problem to try all that in visual studio.
I agree with Alex on this. While I don't have that much experience with ASP. NET deployment and packaging, I would try and move this from build to packaging. For instance, if you could somehow seperate this into a dll or other shared resource, then you could have a different dll for each client. Then when you package for the client it is simply a matter of including the correct dll. This way, you won't miss messages from our team in the future. The first thing you should do, is to make sure that the Visual Studio edition you are using allows the building of bit code.
If you want to develop bit applications using the latest at the time of writing this, of course Visual Studio version, here is a table that will help you understand what Visual Studio edition you will need. If the Visual Studio edition you are using allows the creation of bit code, you should check if the bit compiler is installed.
Figure 1 shows the installation page of Visual Studio components, where installation of the bit compiler is disabled. Difficulties will appear later, when building the new configuration, and searching for errors in it.
To create a bit configuration you should take the following 4 steps:. Choose the bit platform x64 and take the bit version settings as the base Figure 4. Visual Studio environment will automatically modify the settings which impact the build mode. Figure 4 - Choosing x64 as the platform and loading the Win32 configuration as the base. You have now added the new configuration, and may now select the bit configuration version, and start compiling the bit application. Figure 5 shows how to choose the bit building configuration.
If you are lucky, you will not have to adjust the bit project. However, this depends upon the project, its complexity, and the number of libraries being used. The only thing you should modify right away is the stack size. If your project uses the default stack size, i. It is not necessary, but it is better to secure yourself from possible issues beforehand.
0コメント