Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Installing VB.Net on Windows 98SE
- Thread starter wawalter
- Start date
jasonsalas
IS-IT--Management
MS themselves notes that if you are running the beta (which is by its definition, am unfinished product), you should run it on a machine that you can afford to lose. In "Introducing Microsoft .NET" by David S. Platt, ther author notes how running the beta has caused catastrophic errors in PCs, forcing the user to reformat their machines.
But to get back to your query, MS recommends the following system config to run Visual Studio .NET:
Because it's tied in so tightly with IIS5.0 services.
But to get back to your query, MS recommends the following system config to run Visual Studio .NET:
Because it's tied in so tightly with IIS5.0 services.
dilettante
MIS
I did have beta 1 installed on a 98SE box, but have uninstalled it pending arrival of beta 2.
What a dog though. Hopefully beta 2 has been optimized some. Be sure you have a fast machine to use it on.
Truth be told, MS isn't really advocating any development be done on 9x boxes though, and even VS6 has proven more stable for me on NT4, NT5 (2000), and NT5.1 (XP Pro) than on any 9x box.
What a dog though. Hopefully beta 2 has been optimized some. Be sure you have a fast machine to use it on.
Truth be told, MS isn't really advocating any development be done on 9x boxes though, and even VS6 has proven more stable for me on NT4, NT5 (2000), and NT5.1 (XP Pro) than on any 9x box.
jasonsalas
IS-IT--Management
dillettante,
what type of machine were you running it on for your 98 box?
what type of machine were you running it on for your 98 box?
dilettante
MIS
Now don't laugh! Promise!
A Dell Optiplex GX1, 350Mhz PII, 192MB RAM, Win98SE.
Don't laugh, I got it factory refurbed from Dell Leasing w/2 years left on the warranty including OS for $170.
Makes a nice "sacrificial" box for betas. It's so "button-down corporate generic" that I never have troubles with support right off the beta CDs (OS betas).
But I need to bump RAM to 384MB and put in a 600Mhz PIII (fairly cheap upgrades right now) to run VS.Net betas on it.
Got another one I've been using for WinXP Pro betas. Again, no problem with hardware support right off the OS CD. Let's me focus on the software issues I'm interested in and not worry about drivers for oddball hardware.
A Dell Optiplex GX1, 350Mhz PII, 192MB RAM, Win98SE.
Don't laugh, I got it factory refurbed from Dell Leasing w/2 years left on the warranty including OS for $170.
Makes a nice "sacrificial" box for betas. It's so "button-down corporate generic" that I never have troubles with support right off the beta CDs (OS betas).
But I need to bump RAM to 384MB and put in a 600Mhz PIII (fairly cheap upgrades right now) to run VS.Net betas on it.
Got another one I've been using for WinXP Pro betas. Again, no problem with hardware support right off the OS CD. Let's me focus on the software issues I'm interested in and not worry about drivers for oddball hardware.
jasonsalas
IS-IT--Management
Interesting. I'm thinking of installing the .NET Framework CD-ROM on one of my Web production servers at work - a 256MB RAM, 733MHz PIII....I'm just wary about
I'm doing most of my .NET coding now in FrontPage XP (aka FrontPage 2002, aka "WYSIAWYITW" - What You See Isn't Always What You Intended to Write, version 2002"
, since it at least can interpret between .NET script code and raw HTML (earlier version of FP and Visual InterDev 6 won't do this for you) and save files in ASP.NET's native .ASPX format.
The color-coding is still minimal, but it helps a bit....and it better than writing code in Notepad.
I guess if it ran on your machine, I may try it on mine!
p.s. My Web production machine is also largely my workstation...so LOTS of critical files are saved there.
I'm doing most of my .NET coding now in FrontPage XP (aka FrontPage 2002, aka "WYSIAWYITW" - What You See Isn't Always What You Intended to Write, version 2002"
, since it at least can interpret between .NET script code and raw HTML (earlier version of FP and Visual InterDev 6 won't do this for you) and save files in ASP.NET's native .ASPX format.The color-coding is still minimal, but it helps a bit....and it better than writing code in Notepad.
I guess if it ran on your machine, I may try it on mine!
p.s. My Web production machine is also largely my workstation...so LOTS of critical files are saved there.
dilettante
MIS
Yeah jasonsalas, I hear you. VI6 doesn't really like the ASP.Net stuff too much.
I'm noticing that VS6 is starting to really get long in the tooth.
I still haven't figured a way to make use of the "XP visual styles" for VB6 app form controls (command buttons, etc.) in WinXP. You know, the rounded buttons and various rollover color changes and so on. There is a new ComCtl32.dll (v.6) that WinXP has along w/v.5, but you have to create "assemblies" that can ask for the latest and greatest. Else you get the v.5 .dll and your stuff looks like crap on WinXP.
My guess is Windows Installer is required, but that thing's a BEAR at this point. Then again even THAT probably won't do it alone - so I guess I may have to look at the WinXP Beta 2 SDK. Or just forget it for now.
They've upped the ante on icons too. They only provide instructions on using PhotoShop plus somebody's hacked GIF animation editor that'll save the new icon format.
You need four guys to make a decent VB application now: a VB programmer, an HTML Help author, a graphic artist, and a installation specialist. I just cringe at the thought of what it takes to make a commercial C++ program that qualifies for the new logo program!
And I don't believe that VS.Net takes care of any of it for you either - at least in Beta 1. If you've got VS.Net Beta 2 anywhere, have you noticed an improved Package and Deployment Wizard?
I'm noticing that VS6 is starting to really get long in the tooth.
I still haven't figured a way to make use of the "XP visual styles" for VB6 app form controls (command buttons, etc.) in WinXP. You know, the rounded buttons and various rollover color changes and so on. There is a new ComCtl32.dll (v.6) that WinXP has along w/v.5, but you have to create "assemblies" that can ask for the latest and greatest. Else you get the v.5 .dll and your stuff looks like crap on WinXP.
My guess is Windows Installer is required, but that thing's a BEAR at this point. Then again even THAT probably won't do it alone - so I guess I may have to look at the WinXP Beta 2 SDK. Or just forget it for now.
They've upped the ante on icons too. They only provide instructions on using PhotoShop plus somebody's hacked GIF animation editor that'll save the new icon format.
You need four guys to make a decent VB application now: a VB programmer, an HTML Help author, a graphic artist, and a installation specialist. I just cringe at the thought of what it takes to make a commercial C++ program that qualifies for the new logo program!
And I don't believe that VS.Net takes care of any of it for you either - at least in Beta 1. If you've got VS.Net Beta 2 anywhere, have you noticed an improved Package and Deployment Wizard?
- Status
Similar threads
- Question
