Jump to content
Xtreme .Net Talk

isundby

Members
  • Posts

    7
  • Joined

  • Last visited

Everything posted by isundby

  1. Well, I bit the bullet, and re-formatted my hard drive, re-installed Windows XP Pro, and finally VB.NET 2003. It WAS successful ! So I guess I can close this thread. Regards, Ian
  2. Nope. No installation of SQL server here .... I am truly stumped here. I wouldn't mind re-installing again, but I think I need to get rid of EVERY thing that was generated when I initially installed (temporary files, registry entreis, etc.), otherwise, I'm afraid it's going to be the same old, same old..... Thanks. Ian
  3. Yep.... I am current with the critical updates and SP2 Ian ..... P.S. If you are online, perhaps we can chat somewhere..... MSN ?
  4. I have tried the repair. You guessed it.... no good.... Ian
  5. Thanks PentiumGuy. I have never been against that option, aside from the extreme length of time require to do the actual install. I would obviously have to uninstall the MDSN libraries, the .NET Framework SDK, and VB.NET itself. What else do I need to clean up ???? The reason I ask is that when I un-installed and re-installed, the file paths that I installed the components to initially were still active during the re-install, and I did not know what the original destinations were. I don't know if installing to directories other than the defaults can have a negative impact or not, but I would like to ensure that I am right back to the original starting point, if at all possible, if I have to re-install. Is there possibly a rogue registry entry or a temporary file or something ??? Sorry to be a pain. Regards, Ian
  6. Thanks for the reply, Hamlet. At this point, I am simply trying to learn the programming language, but I want to be able to learn to use as much of the functionality of VB and other .NET technologies. As I said above, I am REALLY new to .NET, but I really don't feel like paying MS $99 a shot to get me working properly. As far as I can tell, I setup IIS correctly, but I could be mistaken. I am willing to take some time to get it to work, yet I want to get learning it ASAP, so any help is greatly appreciated. Regards, Ian
  7. Hello everyone. A bit of background .... I am an archaic (20yrs +) Mainframe programmer who is desiring to improve his skill-set (or should I say bring it into the new millenium !!!!), and I have just finished installing (and uninstalling and re-installing) VB.NET, version 2003. I am running into something of a show-stopper here. I am hoping someone can help me with it. I am running Windows XP Pro on an AMD-Athlon system at 1.4 GHz, and a CD-R. When I initially installed, I was requested to update some settings (sorry, can't recall wxactly what they were now). I then went through the basic installation (Prerequisites, VB.NET itself, MDSN library, and service releases. Everything went fine, and I followed all processes to the letter. VB even starts up. However, when I clicked on the MyProfile tab from the Start Page, VB CLOSED down on me. I tried again, and same thing. I then tried clicking on the Online Resources tab, with the same result. The next time I came in, I stayed on the Projects tab, and opened one of the samples identified in the "Getting Started" manual. That opened fine, and allowed me to navigate, and even run the solution. I made changes and saved the updated solution as well with no problem. I can't even create a NEW project/solution without VB closing down. Worst of all, I do not receive any form of error dialog to tell me what went wrong. Obviously, I have done something wrong during my installation, but I do not know what that is. It seems strange that only a PART of VB works. Hopefully, someone can help me with this. Remember, I'm a mainframe programmer/analyst, so you MAY HAVE TO TALK SLOOOOOOW for me to understand ! lol Regards, and thanks in advance.... Ian Sundby
×
×
  • Create New...