Does the version of VS affect opening solutions - visual-studio

I have searched on Google for this, but have had no luck.
I currently have the enterprise edition of VS2012 (paid by my company). If/when I leave the company I assume I will also lose the license and may have to return to the Express version.
I assume the answer is no, but, will there be any problem loading any of projects in a 'downgraded' version of VS2012? I assume all I will lose is the features VS enterprise offers but my project will work fine.

As for me, most valuable limitations of Express versions are
no resource editor
no remote debugger
does not supports folders in solutions, but projects from folder will be accessible, they just will be displayed in the root of solution, rather in folder.
Thought, there much more limitations, but you may not afraid, Express will open your solutions.

Related

IDE gets corrupt after debugging in Visual Studio 2003

My solution currently contains 20 projects in total. These are all window
applications.
But lately after my OS(Windows XP SP3) downloaded updates from Microsoft and after adding just one window form in one of the projects, VS 2003 IDE starts crashing when trying to debug the solution. After crashing VS needs to be reinstall....
ANY advice that might save me from having to reinstall VS2003 over and over?thanks.
I'd disable all addons you might have installed and see if that helps (VS is usually quite stable, but some addons are not). If so, re-enable them one by one to find which one causes the problem
If that doesn't help, see if you can re-create the crash with a minimal solution, and if you can, it might be worth talking with MS about it, their Connect website might be a good place to start.
Please note, if you edit your question to give more specific information (VS version & edition, what projects you're using etc) someone might be able to give a more specific answer, but I think with that generic question, you'll only get generic answers.

Cheaper alternative to VS Team Foundation Server

Is there a fairly inexpensive source control product on the market that integrates into Visual Studio 2008+ and that has the power and capabilities of Visual Studio 2008 Team Foundation Server?
I have used Dynamsoft, SourceGear, Subversion and Platic SCM and reckon that neither of these products can come close to Team Foundation Server.
Ideally I would be interested in a product that:
handles conflict resolution well
handles IDE edits, renames and deletes automatically
easy project management within the source control "server" that allows a project administrator to painlessly manipulate the project structure as they see fit.
Subversion with Tortoise SVN
Here is an article by Rick Strahl on setting everything up.
I used svn at my last job, and tfs at my current one. I can't say I really like having to deal with tfs on a day to day basis.
SubVersion and AnkhSVN will integrate directly into Visual Studio.
Visual SVN is a tool to integrate SVN directly with Visual Studio.
(source: visualsvn.com)
It costs $49 per license.
They have a demo so you can see if it what you are looking for.
Actually, I've recently started using Team Foundation at work. Some of it is nice, but our team has spent at least 10 hours in total last week to fix silly TFS problems that never should have occurred in the first place.
While it isn't perfect, I find Subversion superior in many ways when it comes to plain source control. Get TortoiseSVN and shell out 50 bucks for VisualSVN if you want an integrated solution.
Personally I much prefer SourceGear Vault to SVN.
But it's hard to argue with free, and Vault is pretty expensive if you have more than 2 users.
Try visualsvn.
EDIT
Use VisualSvn as server (my bad, should have clarified I meant that), and as for the client, I used AnkhSVN, which got quite good over time.
From what I hear, VisualHg is a good Visual Studio addin for the Mercurial distributed source-control system. You just need to install TortoiseHg and then VisualHg, and you'll be up and running.
Well, you could use SVN in conjunction with bug tracking solutions such as Trac. There is a Trac Visual Studio plugin. There is also Redmine, though I don't know about its VS plugins.
If all you do is to "view, compare, attach changesets to work items and annotate", I guess bug tracking solutions are quite good.
What features of Team Foundation in particular are you interested in?
If you're just interested in Source Code Control, there are many plugins available for various other products. Subversion for instance has several plugins available which give a very similar experience to the Team Foundation plugin. AnkSVN is my personal favorite.
http://help.collab.net/topic/com.collabnet.anksvn.doc/concepts/ankh_whatis.html
We're going with Git but it probably doesn't have the integration with VS2008 you'd want.
Git manual: http://www.kernel.org/pub/software/scm/git/docs/user-manual.html
Mike,
If you are just looking for source control, the answer is yes.
If you are looking for an inexpensive replacement for everything that TFS does (build, test, project management, etc.) the answer is heck, no.

Is the Team Foundation Server 2010 of the VS 2010 necessary for doing personal projects?

Basically what the title says. I am looking to install the Visual Studio 2010 Beta for compiling personal C++ projects. I haven't made it through the tutorial for setting things up, but do I need the Server part of the program if I don't plan on doing any team projects?
Thanks.
Edit: Well it looks like I can't install the Team Foundation Server anyways without downloading a bunch of other crap. Will the rest of it install without it?
Team Foundation Server is for source control, data collection, reporting, and project tracking. To connect to the server you need the Team Explorer extension installed on your Visual Studio and get a client access license.
I guess you don't need to connect to a server to develop personal projects. For a comparison of Visual C++ 2010 editions, see http://msdn.microsoft.com/en-us/library/hs24szh9(VS.100).aspx.
You don't need TFS 2010 for your personal projects.
1) No, you don't need it.
Unless you really want all the TFS features, you'll be installing masses of stuff for no real gain. Having said that, if you want to use source control, profiling, code analysis and those sort of handy things, it would be one way to achieve this - though you'd probably still be better off with a couple of specific third party tools than the whole TFS install if you only want a few of these tools.
2) No, you don't need to install all the bits to make it work.
Unless something has changed a lot with 2010, the basic VSTS install is more or less the same as the Pro version of VS - and then you install the Team Explorer on top to gain the TFS specific client-side extensions.
In fact, you can go much further by doing a custom install and turning off a lot of stuff that you don't want (VS includes a load of stuff for targetting platforms you will probably never see with languages you may not have even heard of :-). That said, unless disk space is a major concern, it's easier and safer to just go for a standard install, because that is always going to be the best tested configuration - once you start removing bits there is a tendency for odd little things to stop working properly.

Which plugin do you use for SVN in Visual Studio? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I'm considering using SVN for my .Net projects, and I'd like to know what plugins are available for integrating the source control capabilities directly into the Visual Studio IDE.
I already know about the following Visual Studio extensions:
VisualSVN, which seems great but is not free. It is implemented as a low-level VS package extension. Is anyone using it?
AnkhSVN, which is free but I've heard it's a bit buggy. It is implemented as a VS add-in extension. Is anyone using it? are you experiencing problems? Edit: The 2.0 version is a complete rewrite and seems to solve the problem I've heard about (which were related to the 1.x versions)
Edit : TortoiseSVN + Mindscape's FileExplorer VS Extension, which is not a real IDE integration but somewhat eases the use of TortoiseSVN from Visual Studio.
Edit : I've found a few comparison posts between AnkhSVN and VisualSVN here, here and here.
I've used AnkhSVN for the past year and I've never had a problem with it. I switch between that and TFS and some of the times I think I prefer AnkhSVN to TFS.
I use VisualSVN and it works great, but you're correct, it's not free. No experience with Ankh here.
Early versions (1.X) of AnkhSVN were pretty unstable. Latest builds (v2.0.x) work as a native VisualStudio source control provider and it's very stable. I would recommend you to just download and try it yourself.
I also use AnkhSVN and it does work OK but I tend to drop to the file system to work with TortoiseSVN. For some reason I feel safer using Tortoise. I think that come's from concerns about Visual Studio than it is AnkhSsvn.
I tried AnkhSVN, but didn't like it. It tried to do too many things automatically and behind the scenes (e.g. adding files to SVN). I prefer if I see exactly what happens.
Now I mainly use TortoiseSVN (outside Visual Studio) or sometimes Mindscape VS FileExplorer in Visual Studio (which is available for free).
Note: VS FileExplorer plugin simply displays a file explorer in VS and allows you to invoke TortoiseSVN from there (and it also displays the TortoiseSVN overlay icons).
Update:
I reinstalled the current version of AnkhSVN 2.0.5250 and tried to reproduce the problems described above in a sample solution.
Result: AnkhSVN did exactly what I expected. I was not able to reproduce any of the problems. I think it might be time to give AnkhSVN another try at work!
Update 2:
I have now used AnkhSVN for some days, and I have to say it works very well. It's a big improvement compared to the previous version (1.x).
I use AnkhSVN and haven't had any issues worth complaining about. Sometimes (about 1 in 10 times?) I do get a strange nondescript error trying to commit, but restarting VS has always fixed the problem.
Edit: The error actually seems to be coming from the dataset designer, not AnkhSVN. Sometimes I get an error where it tries to "read or write to protected memory", which then just continues until I restart VS. Sorry for the confusion.
I have used both AnkhSVN and VisualSVN each for about 6 months. I prefer VisualSVN for one reason alone: Compatibility.
At my work, we keep our Subversion server and TortoiseSVN software very up-to-date (some people just go with one version and stick with it for years, but that's not our style). With new versions sometimes comes new working copy formats and it seems that AnkhSVN is very slow to adapt these new formats. What happens at this point is AnkhSVN completely breaks:
All the source files appear as "Added" even though they are all committed.
We are no longer able to Commit. An error appears claiming it does not recognize the new format.
VisualSVN has been "on the ball" in this respect as we have never had any compatibility issues with their software. This factor alone easily swayed me toward VisualSVN.
The Agent SVN plug-in does a good job of integrating Subversion and Visual Studio, but it too is not free.
Another vote for visual SVN. To be honest, I think its just me being lazy. I could do everything visual svn does with just using tortoise, but it saves me from switching between programs. The color coded warning lights you get with visual svn are nice, but not that big a deal.
I use VisualSvn and it's fine. It wasn't expensive and it helps make sure you include all files you've added to the solution. It's not so good when using locking in svn (but then svn isn't great at locking files). If you want to edit a file that has needs-lock set, it will automatically update it when you lock it (sensible), but that could end up doing an update when you dont want it too.
I've got into trying Svn Monitor too and am happy with that, but it does seem to grind my computer to a halt.
I've tried old versions of ANKH but got in a mess and corrupted the svn repository (I suspect that was version 1.x) so I'd guess later versions are better.
I use VisualSVN, and love it. It may not be free but I found it extremely reliable, very well integrated, and very much worth the $49 per license. By setting up a few key-bindings comitting and updating become almost second-nature to my entire team (most of whom had no previous SVN/SCC experience).
Being able to quickly scan the solution explorer to see which files had changed was very useful for keeping tabs on things for writing status reports and the like (but that's probably specific to my overly beurocratic manager).
The "Checkout Solution from SVN" feature was great for quickly getting the summer student interns setup and giving them a gentle introduction to version control. Again, this is probably specific to our needs so may not be of interest to you.
So a thumbs-up for VisualSVN and the convenience it gives us.
My experience with working with AnkhSVN is better than tortoise but it still has a lot of flaws that you really don't get with native Visual Studio plugins like Source Safe, TFS, Dynamic soft. It has real problems with the .svn folders and synchronising so you end up spending a portion of your time removing the .svn folder and starting again.
That's my experience. One example is moving a folder from one project (in the same solution) to another project. It breaks on this from the working set being different. The solution is to go into the folder and remove the .svn files but it seems like a a lot of effort.
I'm use to it being a mirror of my filesystem though, and basic 2 developer branches of files.
The AnkhSVN plug-in is not too bad.
I use vsTortoise.
It works very nice especially when you are familiar with TortoiseSVN and it's free.

Source Control in Visual Studio Isolated Shell

I am developing an Isolated Shell that caters to "designers/special content creators" performing specific tasks, using the Shell. As they operate on files, they need to be able to use TFS for source control. This is mainly due to the fact that Developers will also operate on the same files from TFS but using Visual studio 2008.
After looking and searching I still could not find Team Explorer to be available to Shell.
Asking on MSDN forums, lead me to the answer that "this is not supported yet in the Isolated Shell". Well, then the whole point of giving away a shell is not justified, if you want to use a source control system for your files. The idea is not to recreate everything and develop tool windows etc using the TFS provider API.
The Visual Studio Extensibility book by Keyven Nayyeri has an example, which only goes so far into this problem of adding a sc provider.
Has anyone worked on developing Visual Studio 2008 Isolated Shell applications/environment? Please provide comments, questions - anything that you have to share apart from the following threads, which I've already participated in.
Threads from MSDN forums:
Team Explorer for Isolated Shell
Is it possible to use Team Explorer in VS Shell Isolated?
Thanks for your answer. Yes you are right, we will acquire CALs for users without having to buy them Visual Studio, that's the direction we will be taking.
But I am yet to figure out how to make Team Explorer available to such users, inside Shell. So I am looking to find out the technical details of how that can be done.
I mean, I have a user, he installs my VS Shell application, he has no VStudio Team system on his machine. Now if I acquire CAL for TFS and install Team Explorer, do you think it will be automatically available in the VS Shell app?
Any ideas? have you worked on making this happen?
Thanks
It sounds like you are trying to allow the "special content creators" save files in TFS Source Control without having to buy them a license to a Visual Studio Team Edition -- correct me if I'm wrong.
If that's the case, unfortunately I believe that you can't quite do that. Your users still need a Client Access License ("CAL") to access TFS.
I think that you can acquire just CALs for your users without having to buy Visual Studio for them (I presume for less than a full blown Visual Studio would cost). At that point, you can just distribute to them the Team Explorer, which is a VS shell with nothing but TFS access components. That is available in your TFS server media.
I found this via Google. You might want to review it to decide your best options:
Visual Studio Team System 2008 Licensing White Paper
The only exception to the CAL rules I'm aware of is access to Work Items. Assuming properly licensed servers, anyone in your organization can create new Work Items or view and update existing ones created by them, using the Work Item Web Access component.
Just stumbled on this question, it might still be relevant to you.
You have the option of including the AnkhSVN (http://ankhsvn.open.collab.net/) packages and load it into your Isolated Shell. While there are some issues around it, with Subversion support, you could use SvnBridge to access TFS repositories. This might bring you a little bit closer to the process you are trying to achieve.

Resources