Browse by Tags

Tagged Content List
  • Blog Post: VS 2003 Tip #16: Free debuggers

    Life at MS got busy all of a sudden so as a result I blogged less this week. To continue on my last post, the free debuggers we provide are Dbgclr and the command line cordbg. Windbg with sos.dll is a great third one too. The advantages of these debuggers is mostly their lightweight size. Cordbg was...
  • Blog Post: VS 2003 Tip #16: Part I - Free debuggers

    Quick - what are the two free managed debuggers that you can get in Everett (not counting VS 2003)? And if you do know the answer (which I'm fairly certain most do) why do you use them over VS 2003? Let me know what scenarios or why!
  • Blog Post: VS 2003 Tip #15: Attaching devenv to a process from the command line.

    Ziv posted: “I've often wondered how to do the equivalent of "windbg -pn ProcessName" in VS.NET. Is it possible?” I dont know of a way to attach a devenv via a command line to a process by name, but I do know how to do it by Process ID (PID). Just run the following command from a command...
  • Blog Post: VS 2003 Tip #14: Impress your friends with these two arcane tips :-)

    Todays tips are more on the arcane side, but when used effectively at a demo, will elevate you to a semi-godlike status in they eyes of the audience:-) The first deals with attaching to an application to debug it. Sometimes you need to attach to an app to debug it. So you go to Debug.Processes, find...
  • Blog Post: VS 2003 Tip #14: What are the requirements to debug a managed application?

    Every now and then we get a question about debugging managed code with Visual Studio. It is a little confusing so I thought I'd shed some light on it in this post. A canonical example to use here is where you have a web server on some remote machine running ASP.NET code. Something goes wrong on it and...
  • Blog Post: VS 2003 Tip #13: Getting a connection string quickly

    Often I will be writing some quick code to access a database, and I'll need to add a connection string to get this. Heres a quick way to get the connection string using VS: Open Server Explorer. Right click on Data connections and select “Add new connection”. Pass the information that...
  • Blog Post: VS 2003 Tip #12: Better view of data in the debugger windows

    In VS 2003 we did some things in C# to make viewing of data in the debugger easier. The first problem we had was that if you expanded a type, in the watch window, you would get an unsorted list of members. This was a pain if you were searching for a particular member. So we sorted that to begin with...
  • Blog Post: VS 2003 Tip #11: Autocomplete on new class creation

    In Everett we made a small change to Intellisense to lessen the code you had to type. Often you will new up a class and write something like: Foo x = new Foo(); In VS7 you had to type out the whole thing. In Everett we had Intellisense pop up after the new, to autocomplete the class name. This...
  • Blog Post: VS 2003 Tip #10: Run pre and post build commands from the C# projects

    Vs7 customers complained to us that they wanted pre and post build commands that could be run from the project system. Its pretty reasonable to want to automate some tasks that you would do before or after builds, so in Everett we added this in. To get to this feature take any C# project, and check...
  • Blog Post: Vs 2003 Tip#9: Turning off Dynamic Help

    Joen blogs about this here
  • Blog Post: VS 2003 Tip #8: Exception information in the Object browser

    One of the complaints we received from VS7 was that you couldnt tell the exceptions that a particular method could throw. We scratched our heads thinking of ways to do this, as the xml docs did contain this informattion about the class libraries. Ideally we would have liked to have put this information...
  • Blog Post: VS 2003 Tip #7: Implementing interface stubs automatically

    In Everett, we added a feature to add interface stubs to your code automatically, when you wanted to derive from an interface. To do this simply type out “:” after your class name, type your interface to derive from and you should see a little tooltip pop up that says “Press TAB to...
  • Blog Post: VS 2003 Tip #6: Keyboard shortcuts

    I'm a keyboard shortcut junkie. I love keyboard shortcuts for tasks. I've been known when speaking to devs to say stuff like “Ctrl+alt+l, Select foo.cpp, Ctrl+alt_w+1...no, hit Ctrl+alt...” instead of “ Open the solution explorer, select Foo.cpp, open a watch window...”. A while...
  • Blog Post: VS 2003 Tip #5: Intellisense in the immediate window

    Ok, one other new feature we added was to add intellisense to the immediate window. The immediate window is a window used to evaluate expressions, much like the VB6 one. When debugging and in break mode, you can open it up from Debug->Windows->Immediate. Then type in the expression you need...
  • Blog Post: VS 2003 Tip #4: Demo better with the toolbox and task list

    Two quick simple techniques for people who need to demo code (as I wait for the traffic in front of my house to recede before getting to work). Oftentimes, you want to demo some code quickly to people and don't want to type it all in. The Toolbox window is very handy for this. Highlight a bunch of...
  • Blog Post: VS 2003 Tip #3: View exception information with $exception

    Every now and then a feature gets put into the product that just gives you this tickle of excitement every time you think about it. $exception I find is one of those features. Ok - so what scenario would I use it in? Lets say you're writing some managed code. You're debugging your merry way through...
  • Blog Post: VS 2003 Tip #2: Macros

    Vs 2003 allows you to write macros that can automate the IDE. You can acess these through the Macro Explorer - just go to View->Other windows->Macro Explorer and look through the Macros already present there. You'll see we provide a set of sample macros that do various cool things such as automating...
  • Blog Post: Visual Studio 2003 tip #1: Stop the solution explorer flashiness when opening a project!

    A quick note on why I blog about Visual Studio 2003 aka Everett - Its a released product so devs are probably interested in knowing its power features and tips and tricks. I was heavily involved in getting it released for the C# team, so I have a somewhat sentimental attachment to the product...
Page 1 of 1 (18 items)