Install it, configure it in VS.NET's Tools-<Options, then add your projects to source control by right-clicking and selecting Add to Source Control (or from the File-<Source Control) menu. Note, with VSS 6.0 you can either add a solution (not a good idea in most large development projects where developers may want their own solutions with whatever projects they're responsible for) or a single project - you cannot add multiple projects without problems.
From there, you just check out your files, edit them, test them, then check them back in. Never check-in incomplete code (i.e., that won't compile), otherwise you'll cause problems for anyone else.
The best way to learn is to just try it and check out all the options available. It's really not difficult and there's really not a lot of articles that explain the simple stuff - more so just how to managed certain types of projects like ASP.NET sites, which can be a hastle because of their nature. For those types of articles, just see http://msdn.microsoft.com[^].
Sounds simple enough, but there are a few hurdles in the way :
1) I dont have physical access to the machine that will be debugged
2) I cannot install Visual Studio on it, nor run the VS install and just select remote debug tools.
3) The machine I am debugging from is in a standard windows domain, the machine i am debugging to is in a DMZ and cannot see domain logon details - therefore I cannot add myself as a "Debugger Users"
4) I have tried running the debug server with "-anyuser" in "-tcpip" mode but VS still tells me I cannot connect as I need to be part of the "Debugger Users" group
So in summary I need to configure/install remote debugging by transferring the necessary files across the network and then running it in such a way that I am prompted for a user/pass when connecting to the remote debug services or allowing remote debug for any connecting user.
Without physical access or security rights on the remote machine, you're pretty much sunk. You may need to bring IT in on this one, if you can pull them away from all their important work...you know, solitaire, civ, playing XBox in the back room, that sort of stuff.
Once you get install the remote debugging tools, you're pretty much set and you obviously know what you're doing from there.
If you can't install the debugger tools how do you debug it? Remote Debugger is not a way to work around the lack of debugging tools but a tool to use in special cases and this doesn't sound like its applicable.
You are pretty much stuck without a little help from IT. Remote Deubgging is very iffy when crossing sub-net boundries in the first place let alone a machine sitting in a DMZ (connections between the DMZ and trusted nets should be limited by any sane IT admin). Then there is the question of how domains are configured going between the trusted net and the DMZ. They very well maybe completely seperate domains which adds a wrinkle. Besides, installing the Remote Debugger on a production machine might be a security hazard that maintainers don't want to deal with.
The best thing I can recommend is setting up another machine that closely approximates the machine/system in question. Simply put it might be impossible to get the Remote Debugger to work out of a machine in the DMZ because of security policies in place. Without further input from your IT staff who knows what is going wrong. Hopefully you aren't tinkering with live machines in the first place!
I want to use Keypress event in my windows form. When user press enter that time i want to catch that event. and how to use the keypress event because in visual c# i never seen ASCII keys. Tell me how to catch keypress event and use ASCII values for trap the key which is press by the user.
There's many ways of doing this. If you want to catch these in your derivative class, override OnKeyDown. External to your class, handle the KeyDown event. This is to catch and potentially "handle" the key without it being passed to the target window. If you don't care about stopping it from being dispatched, you can handle either KeyPress or KeyUp.
In there, you actually use the KeyEventArgs - not the EventArgs like the other response mentioned - to get the Keys enumeration member for pressed keys, or just the ASCII character value itself. See the documentation for the KeyEventArgs members for more details.
If you want to catch keys throughout your application (say, for configurable hot keys), implement the IMessageFilter class and add your implementing using Application.AddMessageFilter. You get a Message structure that contains the message (such as WM_KEYDOWN) and you can get the data from the WParam and LParam properties. You can also return true to signal that you've handled it and the message should not be dispatched.
i am using visual studio to make some histogram graphs and pie graphs of standered divation but the programme does not recognize the graphics.h header file. how should i make the graphs and please tell what should i do to this heard file (graphics)
I have a problem. I have a login form in visual C# in which user must enter username amd password and then click login. If username or password is blank then one messegebox display that "Please enter username and password". After that i want to exit that sub. In Visual besic .Net there is command "EXIT SUB". In visual C# there is a static method call Application.exit but it is for close the whole application but i want only to exit the event and application should not be close.