net developer.Now a days we work on project with my team members.how to share a project so we can work on a single project and all changes applied on single project rather than we work on multiple projects and then we merge them please can anyone explain me how to do this
In a team, one uses a revision control tool, such as Subversion, Git, TFS, Mercurial or one of many others.
Related
I have been developing ASP.NET websites solo but now I have 2 more developer and I want a tool to share project with them to create a team development environment but I don't want to share my source code with them for example my App_Code folder. I am using Visual Studio 2013 Ultimate Edition for development.
In other words i need an environment where i can share my project with other developers without my App_Code folder files.
Sorry for my bad English.
Create a class library Project and add your sources to it.
Build it in release mode.
Add reference to the output DLL from the main project.
That's about it.
Regarding Source-Control Tools or TFS - it is good to have but will not replace the solution provided and is not focused to provide a solution to your problem.
It just a way to ease team development regarding versioning, bug tracking and etc..
Visual Studio 2012 Express, SQL Server 2012 Express, MVC 4, Code First
I'm looking for a good single user source control solution.
Vault vs Git(hub) vs SVN
From what I've read deployment should happen FROM the source control server, not separately from VS, right? Can Web Deploy be used FROM a source control server?
What would be the best, most cost effective, simplest, easiest Source Control solution? I used SVN a few years ago and it was pretty clunky.
Visual Studio integration is preferred.
There seem to be mixed opinions on how suitable Github would be (very little integration with VS 2012 Express I think?!).
Cloud option would be good to have. Is there a cloud solution that can automatically deploy direct to production server?
(I guess I'm talking about Constant Integration here - though I have zero experience with it, the principle seems like a good one).
Git can now integrate with Visual Studio:
Download here:
http://visualstudiogallery.msdn.microsoft.com/abafc7d6-dcaa-40f4-8a5e-d6724bdb980c
Getting Started guide here:
http://blogs.msdn.com/b/visualstudioalm/archive/2013/01/30/getting-started-with-git-in-visual-studio-and-team-foundation-service.aspx
GIT is your best option.
Integrates with Visual Studio 2012 using the Visual Studio Tools for Git
There are some great Graphical Clients like Github for Windows and Source Tree
Microsoft Team Foundation Server now integrates with Git for automatic deployments with just a Git Push. Scott Hanselman has some great blog posts on how to achieve this here, here and here
Anyways I would strongly recommend taking the free tutorial on Git by Code School http://try.github.io/ (don't be afraid of the command line :P)
VS Express won't support plug-ins, so integration with VS would not be possible AFAIK. Try Tortoise/SVN which integrates with Windows Explorer instead.
For VS 2012 you could use the express edition of Microsoft TFS, which includes version control and a couple other nice perks, more aimed at team dev though.
I know this is a strange situation, but consider a situation where two programmers are working on one project. One programmer is working on a database driven website in ASP.NET in Visual Studio 2012, while other programmer is working on Visual Studio 2008 on another part of the same database driven ASP.NET website.
What in your opinion is the best way to integrate the two codes?
PS: Downvoters please explain in comments, before downvoting. :-)
Make the second developer update his VS copy to 2012. If you are working with two disparate versions of VS, you will very simply be unable to have either developer work on any part of the codebase that was built with (or upgraded to) the other version.
Once everyone's working on the same platform, and thus can load and build the same solution, project and source code files without error, "integrating" the two codebases becomes rather trivial. Of course, the conversion process may not be so trivial.
My first step would be to ensure that a reliable backup of the entire codebase has been taken; you can copy the flat files to a file store, or more reliably you can use a centralized VCS like Subversion to make sure a single authoritative copy of the codebase as-is exists and can be easily retrieved. Then, while the 2008 dev is updating his machine to 2012, have the 2012 developer pull the whole codebase and load whatever solution the 2008 dev had been working in, and run through the conversion wizard. This wizard will update the XML behind the project and solution files to support features of the new IDE version.
If you absolutely positively cannot get both devs onto the same IDE version, there's still hope. Have the 2012 developer open a new solution file in his copy, and pull in the 2008 projects. If VS asks to convert them, you're SOL; the other dev will HAVE to upgrade, or the 2012 dev will have to revert. But, if the IDE doesn't complain, the 2012 dev can save the new solution under a different name and work with the projects and their source code using that solution file, while the 2008 dev can continue to use the original one. Understand that as long as this state of affairs continues, the 2012 dev cannot use any features of C# 4.0/4.5, such as dynamic types, covariance/contravariance keywords, optional parameters/named arguments, async/await keywords, etc cannot be used in any source code that must remain usable by the 2008 dev. Language-wise, the 2012 developer is limited to C# 3.0, and the .NET Framework 3.5. This does not solve the problem of the 2008 dev not having access to code written from scratch by the 2012 dev in projects created by that IDE; he simply must upgrade to work in these parts of the codebase.
Well I intend to host the group projects assigned by my Professor to a service like GitHub or CodePlex. I even have made an account on CodePlex to get started. What I am confused about is which is the most easiest to use for beginners like me or my Team members. Moreover which source control system to use with Visual Studio 2010 Professional? Any links or tutorials will be helpful for me.
Plus: Which license to use for Personal Projects?
If you're using VS Professional and working in a team, then I suggest trying Team Foundation Server with CodePlex.
TortoiseGit is very easy to use to manage GitHub repositories.
To integrate Git with visual studio, you can try Git Source Control Provider.
I'd like to understand the proper way to build the MVVM toolkit from the source files on codeplex for a WP7 sample app. I've got the source associated with codeplex changset 47157 by lbugnion Apr 18 at 10:42 AM 1300 associated with Release: MVVM Light Toolkit V3 SP1 (2).
I've got VS2010 and Windows Phone Developer tools installed. I see the VS10 dir that presumably contains the VS2010 solution files. Do I just open that .sln file in VS2010 and build all? The distributed binaries contain versions of the dlls suffixed with WP7. I don't see those version of the dlls generated when I build the VS10 solution file.
Thanks,
Peter
There seems to be a problem with the WP7 bits. Unfortunately they are missing from the VS10 folder and are instead in the old GalaSoft.MvvmLight folder. Plain and short, I messed up. The "old" folder was historically the root. When I added projects for SL4 and WPF4, I did so in the VS10 subfolder (not my brightest idea). And when I added WP7, I apparently did so in the wrong folder. This is really weird.
I have a flaky internet connection in the moment (I am on the road) so I won't be able to fix the issue before a couple of days. I made a note and will fix the CodePlex code base ASAP. More info will be given on my blog http://blog.galasoft.ch.
Cheers,
Laurent
If you're using Visual Studio 2010 the solution you should open is source\VS10\GalaSoft.MvvmLight\GalaSoft.MvvmLight.sln. The Silverlight projects may not open if you don't have the Silverlight Tools for Visual Studio installed. Don't worry about this if you're only building the WP7 version of the toolkit assemblies. The solution structure is confusing at first because it uses linked file references.
Actually, now that I look at the VS10 solution, it doesn't look like there are any WP7 files under the structure. I think you're correct, and the Visual Studio 2010 solution doesn't build the Windows Phone 7 assemblies.