I've been having this problem with visual studio that I cannot seem to find a simple answer to. I would like to be able to save out versions of my visual studio project so that I can test a concept I have in mind that may dramatically change my code and if I do not like the outcome, I would like to be able to load up a older (previous) version of my project. Every googled answer I have found for this problem has been some kind of big professional development version control software. Its crazy to me that there is not a simpler way. I suppose I could copy and paste my project dir each time I want to save a "version" and just rename it, but this seems rather archaic. I use many graphic applications that simply have a "save as with new version" feature and I can easelly load and version I have saved.
any advice would be amazingly helpful.
thank you!!!
Just use git!
https://git-for-windows.github.io/
It is a very simple light weight version control system, that will do everything you are asking for. It is free, and should only take a few minutes to set up.
Related
I've been googling this all afternoon and I found any number of people ask the question, and all of the place a few people would answer it with the same things, and then there's a dozen comments by the rest of the world and the OP about how those answer don't fix it. So I'm going to include what I've tried here, and if your solution is to do one of the things I've already tried, I'm going to be very sad.
I have a solution in Visual Studio 2019 that has a class library, a wpf application, and a setup project (using the setup project extension). The WPF app also references a bunch of assemblies of course, but one of those is from another project I maintain in a different solution. I copy/paste the compiled dll after I update it from its own project to this one. Nothing tricky, everything works.
The problem is the installer. If I build everything and then build the installer, it produces an MSI as expected. If I right click on the project in Visual Studio and choose "Install", everything is perfect.
The problem is after I make some updates to either of the code projects, I then build both and build the setup project, and again if I right click to install it's perfect. If I run the MSI though, it doesn't always update the target files. If I delete the target files it will create them with the new ones, but it won't overwrite the old ones correctly.
AssemblyVersion and AssemblyFileVersion are both being incremented each time and are being kept in sync with the "Version" property of the setup project. I tested with these extensively, the new installer that isn't working properly 100% has updated dlls in it with correctly updated version numbers.
When I change the "version" of the setup, it asks to change the GUID for the ProductCode. I say yes, it changes the code. I have also tested without doing this and that makes it much worse as we all know.
"RemovePreviousVersions" is set to "true" in the installer project
If I right click the project and choose "Install" it seems to be 100% reliable at upgrading the existing installation.
If I run the MSI directly it seems to be 100% unreliable and never gets it right.
Side note, it does seem to usually but not always get the WPF application upgraded and the other project dll I bring in if I remember to update its version, but the class library (which is referenced by the WPF application) almost never works.
Has anyone got this to work reliably?
For all the people finding this in the future, here's the final word:
The build project can be inconsistent, this is well documented all over the internet as I have above. You're not doing anything wrong - it is just inconsistent.
Stop trying to solve it if it's affecting your project and move on (I've had a dozen projects before this one work just fine). The consensus seems to be to use WiX, but I'm not here to discuss the alternatives. Personally I am going to embark on the WiX learning curve though.
Okay, so, really quick question that I hope I can provide enough detail to get an answer for.
Programs used: Visual Studio 2015, Github
The problem is occurring whenever the developer makes a change that includes the references within Visual Studio and commits his changes to our Github. I am our tester and am told that the code is ready for testing, only to find that I cannot compile at times due to the Project References not being correct. We have discovered that this is because Github does not synch changes to the References that a Project has. The Reference that is giving us the most problems is an internal reference to another project within the solution, and appears in the "Shared Projects" section of the Reference Manager in VS2015. The developer is trying to soothe these issues as well, but our progress is being slowed significantly by this problem while he searches for an in-code solution.
Is there a way to force Github to add these Reference changes when making a commit? Due to the terminology used, I have not been able to find a solution to the problem anywhere, or at least one that I understood. I am not well versed in Visual Studio, so I am not sure if there is an option to change somewhere or another simple fix. If there is, please let me know.
I hope that I have provided adequate information without breaking my company's NDA. If you need further info to aid in this matter, I can ask the developer for further clarification, although it may take up to 24 hours for him to respond. Thank you in advance!
When I try to install the Async CTP for Visual Studio 2010 the installer fails.
I got the same problem bob mujica described in http://social.msdn.microsoft.com/Forums/en-US/netfxsetup/thread/2b816f97-ba1a-4342-824f-07c53f946b57.
Now Visual Studio doesn't work at all. I don't care about having CTP, I just want Visual Studio back. Does anyone know how I can do this?
Ian,
I know it won't help in this scenario but a little advice for the future that could save a lot of heartache. for the past 7-8 years, i've got into a disciplined habit of making a fresh backup (ghost) of my program partition (genarally the c:\ drive in my case) everytime i add a new program feature (other than service packs etc) to my installation. This basically means that should something 'not work' after installing, I can simply restore the ghost image over the top, rather than spend hours trying to figure why.
As i said, may not help this time but is a good discipline to work towards in the future.
My recommendation would be to install a fresh copy of Visual Studio, or perhaps to copy files from a fresh installation to overwrite any updated libraries. Assuming that you have the installation media you could also try to repair the installation from Control Panel -> Programs (Add/Remove Programs if you're still on XP).
From the linked post it sounds like either (a) a library file has been overwritten with an incompatible version or (b) a library file is referenced but not found on the system. (a) likely can be fixed by trying any of the above. (b) most likely requires VS to be removed and reinstalled from scratch. If you have a second machine around, you could try installing VS on that and dump or record the relevant registry changes and compare it with the faulty installation, but it might be faster just to reinstall.
what is sourcesafe?
i am trying to download it to see if it will work well with c# because someone told me to download it for a job, but i don't even understand what it is?
is it built into the visual studio ide or what?
SourceSafe is a poor and obsolete source control system.
It can store an application's source code and show revision history, and allow multiple developers to work on the same project efficiently.
It has been replaced by Team Foundation Server.
Sourcesafe is a version control system from Microsoft, some would say not a very good one. It's not part of Visual studio however it does integrate into it. MS have now replaced VSS in their Team System version of Visual Studio.
Source control is a great idea, and experience with them will definitely help your Job hunting, but don't constrain yourself to Sourcesafe, also checkout (pun intended) systems like Subversion etc.
I'm starting a new project in MonoDevelop, and I want to see how other projects are using it.
I tried searching through SourceForge, code.google.com, etc., but mostly I was just finding things like add ins or something related to MonoDevelop itself.
So is there anyone else using MonoDevelop, especially open source?
Basically, MonoDevelop is designed to function very similar to Visual Studio, including using all the same sln/proj file types. You can take a VS solution, open it in MD, and hit F5 to run it, and vice versa.
Because of this, I don't know that many people are going to write about "how they use MD as part of their project" any more than someone is going to write about how they use Notepad.
Any project that is using sln/proj files on Linux/Mac is likely using MD.
MonoDevelop is multiplatform IDE, especially for Linux. Works with Visual Studio solution and project files (100% both direction compatibility). So you can't find project using it. Any C#/VB.NET project can be developed in MD.
Three years ago me and a friend started work a new mono project and tried to use MonoDevelop for it. However - this was an impossible mission - we got ridden with all kinds of bugs and crashes and in the end I said - go to hell MonoDevelop - I'll use my tried and true Emacs.
To tell you the truth with no features other than formatting and font locking Emacs turned out to be 10 times more productive environment for me. My friend somehow endured using MonoDevelop for the whole run of the project, but afterwards he said he was done with Linux for good if it offered such low quality dev tools.
Times were different back then, I've been following mono's development and monodevelop's as well - they seem to be turning out quite well. I think that the actual cause of your problem - not finding anything - lies in the fact that most Linux devs openly shun Mono as a development platform because of it's Microsoft roots. This is sad - because it's a solid alternative of Java - especially at the desktop applications front(GTK# is seriously cool).
Banshee seems to be using MonoDevelop. Probably most of the prominent mono projects with a GUI use it as well to some extent.
I've found MonoDevelop to be excellent so far. I've only been using it for about a month, but once I got it set-up the way I want it, I wouldn't go back to any other editor or IDE on Linux. It took me a while to figure out how to set the debugger up and configure the editor to how I like it.
It's almost like having Visual C# Express on Linux.
Try searching for MonoTouch projects. Mac + MonoDevelop + .NET iPhone apps.
I just tried compiling my project, 2 problems:
couldn't load Setup projects
couldn't load SQL Server Library projects
There is a way around this of course, just have to consider that not all project types can be built in mono and must design solution the way it doesn't stop you from building what you want.