A little Q&A


Reader Dave asks:



I am using Visual Studio 7.0 (2002?). I turn on my computer in the morning, and run it until midnight and my visual studio is always open. however, it consumes 60-150MB Virtual memory, specifically when i use VisualPerl (I usually use Visual C++). sometimes i need to run two instances of visual studio, but virtual memory usage keeps growing in both processes. do you know any fixes, or suggestions?


I talked to some of the people who are involved in providing support for previous versions (something at Microsoft that is typically dubbed “sustained engineering“).  They tell me that, unfortunately, memory leaks in the IDE (such as the one you are experiencing) are typically low-priority, and not as likely to be fixed as language design flaws or serious limitations in compiler functionality.  The fact that the problem is most noticable in a third party add-in suggests it might not even be a problem primarily with the VS product.  My only suggestions in this area are to contact ActiveState, to see if they are working on a fix for your problem, or to install any relevant VS .NET 2002 updates. (Though, it doesn’t appear there are any addressing this specific problem.)



as i have posted in my prior posts, i have never used .net. i will say one more thing, but i dont know if it is correct, so it contains a question as well; we dont need windows forms or anything else dealing with user-interface to run a service at the server, right?


That’s correct, you don’t need windows forms to write a service.  Windows forms are just a way to describe user interface – typically, services (especially FreeBSD/Linux/etc. ones) handle user interface through config files, command-line options, or some kind of limited console interaction.  All of which should be supported by Rotor through the various CLI namespaces (System::Console, System::IO, etc.).

Comments (2)

  1. Dave says:

    Hi Andy,

    thanks a lot for answering those questions. I thought there could be a fix for my poor vs 2002, but anyways, I keep restarting the ide.

    today, I have started my first visual c++ .net application, but I didn’t find any user interface example in the documentation coming with vs2002, but I am really into it. I am familiar with classical win32 api, I was using WTL and it was quite simple to build a good user interface in few minutes. Btw, I have found another problem with my vs2002; I cannot see "Visual C++ Directories", when I go to Tools->Options->Project Settings (I need to change C:WTL70include -> C:WTL71include, I have downloaded WTL 7.1). This directory thing doesnt appear. I have used Winspy (a third party app) to see, if the window is around but I cannot see it (not WS_VISIBLE?), however child dialog the directories listbox (was that a list box anyway) should be created in doesnt contain anything. anyway, it seems microsoft does not support visual studio 2002 anymore.

    back to lack of visual c++ .net examples. I saw that there are lots of c# examples, this is good because C# is a new language and if i am correct, it is built for .net. there are vb.net examples, too, but there is not a visual c++ .net example displaying a window on the screen (or i didnt see any). so i am playing with console and sockets, and it is getting boring.

    i see whidbey samples everywhere, in your blog for instance, but not much examples for vs2002. it seems i need to upgrade vs2003 as soon as possible.

    Thanks a lot, again.

  2. Dave says:

    Hi again,

    I went to barnes & noble site, and found "Programming with Microsoft Visual C++ .Net Managed Extensions", Richard Grimes, August 2002 from Microsoft Press. I am going to buy this book, hope it helps.

    In fact, I need to start from the basic things, learn more about .net (or clr) architecture, but you know; every programmer wants to display something on the screen, and its for sure "hello world" brings you ten years ago and make you feel you are starting from the beginning again (it feels like you start walking from earth to mars, and you are missing your house before you are shuting the door) :/ But, a programmer should not take things in such a romantic way, and must read && learn if s/he really needs it. (am i too sensual? hah!)

    anyway, its time to buy the book (then visual studio 2003).