Does anyone know how to get a project up there? I have it all set up I just don't know how to get my project uploaded, thanks guys!
Printable View
Does anyone know how to get a project up there? I have it all set up I just don't know how to get my project uploaded, thanks guys!
You need to read this and decide how you're going to upload code.
Thats the part im having trouble with. I've never used source control or anything of that nature. I have Visual Studio 2008. And to be honest I have never actually released a project per se. I have released many .DLL's but they are simply copy and paste!
I notice this one: Team Explorer: A GUI source control client that can run stand-alone or integrates with Visual Studio 2005 or 2008.
What exactly does it add to my installation. Sorry if I sound noobish!
It doesn't add to the installation, it simply tells VS that the project's under source control so it'll allow you to check files in and out for editing and VS can keep track of the changes made when files are checked out.
Ok, so if I download Team Explorer I can put the whole application on code plex? Is it stored the same way that we do it here, (basicly the whole directory for the project) or does the compiled application AND the source get stored? also what I meant by adding to the installation was this:
!! Warning !! - If you use the Team Explorer client then it will add source control binding information into your project files. When users download your source code and try to open it in Visual Studio they will get error messages because of the source control bindings. You can use any of the other available source control clients as an alternative.
Does this mean that if some downloads my project to play with they cannot?
I personally used the Codeplex client, which is a standalone, command-line utility and does not mess anything up. In the link I've provided, there are instructions on how to use it.
I am currently using Team Explorer for a project I am helping with on CodePlex and thus far, apart from a slight learning curve am not having any problems with it. The Source Control bindings are simply the way that Team Explorer maintains the references to all the project files. If someone else who is contributing to the project isn't using Team Explorer then they are not going to be able to check in changes.Quote:
Originally Posted by DeanMc
Gary
So the binding only effects the code im working on not the code released for general download?
That would be right. Normally you would create a release package, i.e. an msi, and that would be the release.
Ah ok now that makes sense. So does teamserver look after uploading that package and/or any release notes?
No, you take care of that yourself. I added a project to CodePlex by first creating a CodePlex project, setting up the workspace to point to a 'local' folder, moving my solution into that, and then in Team Explorer, adding the files straight in. That was it.
The next time you open the solution it'll ask you to re-bind the solution, it's a simple matter of clicking each line (one per project) and clicking the bind button.
For the release setup file, on CodePlex, you go to the release page and upload the latest installer. You can also add release notes there.
Cool, thanks guys!