projects-and-solutions

I want to convert projects and solutions between VS2005, VS2008 and VS2010. For Example from VS2010 to Vs2005 or 2008 to VS2010, from VS2008 to Vs2005. Is there that tool exist? There is project converter for versions 2005-2012 on Codeplex . There is another project converter for versions 2002-2008 on Sourceforge . 来源： https://stackoverflow.com/questions/9600027/is-there-a-tool-to-convert-between-vs2005-vs2008-and-vs2010-solutions-and-proje

I need to add event calendar functionality to my application, and I'm wondering what do you think is the best way to do it ? Are there any interesting projects providing the needed functionality ? A snippet : http://djangosnippets.org/snippets/129/ ? Write it on my own ? Without knowing the level of complexity you need, I always suggest quick and easy first. Once minimum requirements are established you can confidently migrate. Django Flatpages can take you a long way with very little effort. If you're looking to go all the way, setting up a DAViCal server with some kind of python bindings

I think it is quite normal to have more than one binary in a project. However, with Eclipse CDT I don't know how to set up the IDE to get things done. I know I can create several projects - one per binary. And I know I can set the dependencies per project. However, I cannot regard them as one project in Eclipse. If I'd like to share the code with a version control system (like svn), each developer has to import the projects separately. What I miss is something like the Solution (sln file) in Visual Studio. Should I create a single project and create the make files by myself? I haven't tried it

In our company we have staging and production servers. I'm trying to have them in state 1:1 after latest release. We've got web application running on several host and many instances of it. The issue is that I am an advocate of having the same architecture (structure) of web applications on staging and production servers to easily test new features and avoid creating of new bugs with new releases. But not everyone agree with me, and for them is not a such big deal to have different connection between staging application instances. Even maybe to have more application and connections between

I don't see it in the .sln file, which is what I expected. Which project is the "startup" project only has any relevance for debugging, which means it's user metadata from the point of the solution and the projects. Regardless of which project is the "startup" project, the compiled code is the same. Because of this, the information is stored as a user setting in the Solution User Options file (solution.suo) which accompanies the Solution file (solution.sln). The .suo file "Records all of the options that you might associate with your solution so that each time you open it, it includes

I was wondering what's the best approach to reference a project in the same solution. Do you create the reference using the 'Add reference' feature or do you 'manage the nuget package' and download a certain published version. Each project in its turn will result in a Nuget package which can be referenced by other solutions. So for other solutions it's clear. They create the reference using Nuget, but how about intrasolution project references? The best approach is to create a NuGet dependency on the referenced project. Suppose you have two projects in your solution: Solution | ProjectA |

We Have a large VS solution using project references which is build by TFS Build like so: Solution - Project 1 - Project 2 - Project ... - Project N Because the solution is too large we have several smaller solutions which we use day to day: SubSolution - Project 1 - Project 19 The problem is that developers working on SubSolution find that it is not building because the project references could not be found, so they change the projects to use file references. This then goes on to break the TFS Build which cannot find these file references because they have not been built yet (Even though the