|
I have the guts of it spread out in front of me right now. I was hoping to have it done last year but there was a serious memory leak with ASP when you installed .NET that no one bothered mentioning (and was only fixed in the release candidates). We're now back on track but it's slow going since it's only me and potentially Erik Thompson doing the grunt work.
The hardest part of moving from ASP to ASP .NET is getting out of the bad habits ASP induces.
cheers,
Chris Maunder
|
|
|
|
|
Right, you've sold me. Speed and no more VBScript. I'll drink to that!
Chris Maunder wrote:
when you want to install new server side components you just copy them in. ASP .NET no longer locks components, so when it sees a new one it bleeds off users from the old one, reloads the new one and continues on. No more restart hassles.
".....and their was much rejoicing and merriment"
Giles
|
|
|
|
|
Giles wrote:
Hi Paul,
Got My MSDN subscription, but have been too busy to have a look at it yet, since Beta 1. Whats so good about ASP.NET? I work on a load of server side stuff, and as such like my C++. In a way I like the sound of .NET. I know when I'm doing client side stuff and I produce and install, I get the answer from users "I have not got admin rights to install this - need to call the help desk".
Go on why is it so good. I'm sure it must be, but I fear current projects will tunr me into a dinosaur in the next 6 months. Need help. I can see your the man to put me straight.
Giles
I was about to reply to this and then I read Chris's reply. Was his sufficient or should I add some more ASP.NET features?
I think he very adequatley covered WHY we NEED ASP.NET
regards,
Paul Watson
Bluegrass
Cape Town, South Africa
"The greatest thing you will ever learn is to love, and be loved in return" - Moulin Rouge
Martin Marvinski wrote:
Unfortunatly Deep Throat isn't my cup of tea
Do you Sonork? I do! 100.9903 Stormfront
|
|
|
|
|
Hi folks,
Has Microsoft cooperated product activatin in their final VS.NET? I mean shall we register online to activate the product?
Cheers,
Mehdi
|
|
|
|
|
Since when has product activation required you to register with Microsoft?
________________
David Wulff
http://www.davidwulff.co.uk
"My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group, there was less competition there" - Gandhi
|
|
|
|
|
You get a product code when you download VS.NET.
Jon Sagara
What about ?
|
|
|
|
|
I doubt if we'll be switching to VC7 at work for the foreseeable future. There's just no compelling reason to do so. (I think) We have a universal MSDN subscription at work, but we're still not going to install any of the new stuff.
As far as using it at home, I simply can't afford it. Even if I could afford it, I'm not sure I'd want to. I heard that the new MSDN stuff requires activation (like XP does), and I'm not willing to do that.
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
I have to agree with John here on the 'it costs too much'.
I don't understand why MS got rid of the VC Pro version. VC Standard lacks features that I use (at least VC6 did). The only way to get VC Pro is to buy VS Pro.
BOOOOO HISSSSSS
Tim Smith
Descartes Systems Sciences, Inc.
|
|
|
|
|
S'okay - I have my wood ship models to fall back on now. I may never program at home again.
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
I learnt my lesson a long time ago, never upgrade your development tools whilst in the middle of a project. No matter how cool the new stuff might look or how much I want to use the new IDE - I can't use the new one.
My current contract project won't be complete for a while yet so I'm stuck using VC6 commerically for a while.
When my MSDN subscription dvd's arrive, then I will install VS.NET on my home machine and have a play. There won't be any commercial work done on it for a bit.
Michael
|
|
|
|
|
I agree with this. A better phrasing might have been "When do you expect to use VS.NET for production usage?"
I have it but my first task to to evaluate how much work is needed to port existing code and then when to make the transition.
|
|
|
|
|
I wish my company could be forced [by me] to upgrade
Nish
Sonork ID 100.9786 voidmain
www.busterboy.org
If you don't find me on CP, I'll be at Bob's HungOut
|
|
|
|
|
Hi Nish,
I know how you feel, but I finally beat mine into getting it. We have all the hardware we need but not the software. Like getting blood out of a stone on that side.
I remeber until last August we were not alowd to even purchase a copy of Win2K of Office 2000, to even install in a test environment on an isolated network, becaus it was not corporate approved.
I then went down the road of asking them about a piece of sharware - is this corporate approved - they go uh? - then how about this I coded? if this corporate approved.....
Those guys have sice shown themselves to be ingnorant monkeys with more power than they deserve.
Yes I shall shut up. Has nothing to do with your problem, but yet it does. Stops us from being as creative as we think we can be. But I think I remeber you recently pointing out something about picking a word out of a dictionary.
Sorry my mind is wandering out of control.
Giles
|
|
|
|
|
1. I will wait to see the next two new frameworks from Microsoft before deciding whether to upgrade to .NET or not.
2. I will upgrade only if C# becomes cross-platform (in other words, upgrade to java).
3. Now I have seen .NET, I can finally upgrade to COM now ...
|
|
|
|
|
I think Chris M removed the text option after 90% of the text answers turned out to be trash typed in by idiots.
Nish
p.s. Your text answers are quite valid though.
Sonork ID 100.9786 voidmain
www.busterboy.org
If you don't find me on CP, I'll be at Bob's HungOut
|
|
|
|
|
Nah - I just was curious as to a timeline or an indication of yea/nea. Besides, without the text box we get more comments
cheers,
Chris Maunder
|
|
|
|
|
AReader wrote:
I will upgrade only if C# becomes cross-platform (in other words, upgrade to java).
Bwhahahahaha !! Well said...
Christian
I have come to clean zee pooollll. - Michael Martin Dec 30, 2001
Sonork ID 100.10002:MeanManOzI live in Bob's HungOut now
|
|
|
|
|
AReader wrote:
. I will upgrade only if C# becomes cross-platform (in other words, upgrade to java).
Java, cross platform... good one!
regards,
Paul Watson
Bluegrass
Cape Town, South Africa
"The greatest thing you will ever learn is to love, and be loved in return" - Moulin Rouge
Martin Marvinski wrote:
Unfortunatly Deep Throat isn't my cup of tea
Do you Sonork? I do! 100.9903 Stormfront
|
|
|
|
|
Java, cross platform... good one!
Perhaps the following is funnier: At a .NET training class in my company, the consultant giving the speach was talking about the platform-independent CLR layer (or something like that), a listener asked the question "Do you mean CLR is or will be ported to different platforms?", the answer - "It is already working on various win32 platforms".
|
|
|
|
|
It's not the first time that I heard what some people think about .NET's cross-platform capability. Here is another quote from MSDN:
A second obvious benefit of MSIL is that it decouples your EXEs and DLLs from any specific operating system or hardware platform. Microsoft currently has plans to ship a version of the CLR for Windows 2000, Windows NT®, Windows 98, and Windows 95
To be honest on the topic, Ximian is working on a project called Mono, which will *hopefully* port .NET apps to platforms other than WinTels.
// Fazlul
Get RadVC today! Play RAD in VC++
http://www.capitolsoft.com
|
|
|
|
|
MSDN:
A second obvious benefit of MSIL is that it decouples your EXEs and DLLs from any specific operating system or hardware platform. Microsoft currently has plans to ship a version of the CLR for Windows 2000, Windows NT®, Windows 98, and Windows 95
Call me old fashioned, I just don't think Win32 operating systems can be called multi-platform. Otherwise, I would have been writing platform-independent code for as long as I had been a programmer.
As to porting .NET to something other than Win32, I don't believe it will succeed. Microsoft will focus on something other than .NET long before people have time to finish porting it. Remember, COM was supposed to be platform-independent.
|
|
|
|
|
AnonGuy wrote:
Remember, COM was supposed to be platform-independent
Was it?
I thought it was only language and protocol independent!
Nish
Sonork ID 100.9786 voidmain
www.busterboy.org
If you don't find me on CP, I'll be at Bob's HungOut
|
|
|
|
|
Well, COM was supposed to become available on multiple platforms to make it more competitive with CORBA. I believe a company called Software A.G. (in Germany) got COM working on several UNIX platforms. I'm pretty sure it wasn't free though, like it is for Windows.
Regards,
Alvaro
|
|
|
|
|
MS is also porting C# and a subset of the CLI to FreeBSD.
cheers,
Chris Maunder
|
|
|
|
|
So that's how they are going convert Hotmail to .NET
Michael
|
|
|
|