Hello again StackOverflow. I am getting back into developing in XNA/C# with a few buddies of mine across the states. I have setup a server on my computer, installed TFS and Sharepoint, but neither of these seems to have the exact solution that im looking for. I want to be able to share a project with multiple other people, and preferably at the same time be able to edit (dont know if this is possible, ive seen it done with HeroEngine and a few other programs) What is the best way to acheive this? I know I can set up a shared folder with the project in it, but I feel there are many faults to this as version control and overwriting other peoples work. What is the best solution for this?
Related
I have two questions, I am pretty much inexperienced in this kind of stuffs and this is my first time I want to do this so I appreciate if you give me a clean guideline and if it's possible without too many jargons.
what is the simplest way to make an installation setup for my app.exe file? I saw some answers about WIX, is it simple?
2.This is my important issue, how can I make sure the client can only installs this application on only one system. He can buy one and installs on his own computer but not any other system after that.
I would appreciate If you help me with some links to easy to follow guides, I am a total newbie in this Area and this is my first time using windows and visual studio so I am not very familiar with them.
Application Insights has a great feature that can open an execption in Visual Studio and then debug with the current state of all the variables and objects.
I have been looking around for a open source alternative that can do the same, but I have not found anything similar. What I want to achive is quite simple. I want to dump all the state of my objects/variables when an exception occours, save it somewhere and then later on be able to load it into Visual Studio.
Any ideas how to achieve this?
Application Insights appears to be an Application Performance Monitoring tool.
These generally seem to be language/platform specific, but the best known open source alternative I could find is called insepctIT, which is for the Java ecosystem.
It appears that you can cobble together multiple tools to get the same job done in other ecosystems, OpenAPM seems to have a tool that lets you compare different pieces of the overall APM workflow and put together a monitoring solution for your app.
I realize this doesn't solve the specifics of your question related to debugging in Visual Studio, but it could help others that run across this question on google.
Me and few friends are going to participate in Ludum Dare in a few hours as a team. We wonder how to effectively work with Unity and VisualStudio together on multiple computers.
The first idea was to use git/svn but it turned out to be very annoying as we need to commit/push/pull way too often even for some minor changes such as some Unity button.
The second thought is to use Dropbox or some service like that. However, when .sln file is somehow changed, the project at the otherone's computer must be completely refreshed and it usually ends with import errors.
Could you give us some tips how to collaborate on the same project together as much effectively as possible?
Well we finally figured it out! The solution is to use Visual Code instead of Visual Studio. Then you may use Dropbox but you mustn´t sync Assembly-CSharp.csproj if your team use multiple operating systems.
Since the connection with the TFS server at my office is not stable, I often work with the codes in offline mode (here's how to work offline quickly).
The regular problem I get after the system goes online is the merging step which makes me stumble around the codes to get the codes online. I don't understand why the same problem doesn't happen when I work online from the beginning!
So, my question is what are the problems when working offline with TFS? And their solutions/notices to get back to online codes?
If you want to insure that you will not have to merge, you can check out a file or files with the lock option. This does not allow anyone to either check in or check-out on that particular file while you have it locked.
Understand that this could hamper productivity with fellow workers if they need to edit that same file.
Documentation is here.
Is anyone out there using Team Foundation Server within a team that is geographically distributed? We're in the UK, trying work with a team in Australia and we're finding it quite tough.
Our main two issues are:
Things are being checked out to us without us asking on a get latest.
Even when using a proxy, most thing take a while to happen.
Lots of really annoying little things like this are hardening our arteries, stopping us from delivering code and is frankly creating a user experience akin to pushing golden syrup up a sand dune.
Is anyone out there actually using TFS in this manner, on a daily basis with (relative) success?
If so, do you have any hints, tips, tricks or gotchas that would be worth knowing?
P.S. Upgrading to CruiseControl.NET is not an option.
Definitely upgrade to TFS 2008 and Visual Studio 2008, as it is the "v2" version of Team System in every way. Fixes lots of small and medium sized problems.
As for "things being randomly checked out" this is almost always due to Visual Studio deciding to edit files on your behalf. Try getting latest from the Team Explorer, with nothing open in Visual Studio, and see if that behavior persists. I bet it won't!
Multiple TFS servers is a bad idea. Make sure your proxy is configured correctly, as it caches repeated GETs. That said, TFS is a server connected model, so it'll always be a bit slower than true "offline" source control systems.
Also, if you could edit your question to contain more specific complaints or details, that would help -- right now it's awfully vague, so I can't answer very well.
We use TFS with a somewhat distributed team - they aren't too far away but connect via a slow and unreliable VPN.
For your first issue, get latest on checkout is not the default behaviour. (Here's an explanation) There is an add-in that will do it for you, though.
Here's the workflow that works for us:
Get latest
Build and verify nothing's broken
Work (changes pended)
Get latest again
Deal with merge conflicts
Build and verify nothing's broken
Check in
[edit] OK looks like you rephrased this part of the question. Yes, Jeff's right, VS decides to check some files out "for you," like sln and proj files. It also automatically checks out any source file that you edit (that's what you want though, right? although you can change that setting in tools > options > source control)
The proxy apparently takes a while to get ramped up (we don't use it) but once it has cached most of the tree it's supposed to be pretty quick. Can you do some monitoring and find the bottleneck(s)?
Anything else giving you trouble, other than get-latest-on-checkout and speed?
From my understanding you can have multiple TFS Application servers in different locations. They either can both talk to the same SQL Server or you could use SQL Server mirroring. Having your own local TFS server would likely speed up your development times.