The latest version of the CLR brings 64bit compatability. As for companies jumping ship, I've heard some of both (jumping on and off that is)...but neither of what your or I hear is really valid as far as looking at the entire landscape.....only time will tell.
Wow, I actually managed to find where I got that number from....
http://www.joelonsoftware.com/articles/APIWar.ht ml (search for 375 and you'll see the part where he mentions it)
http://members.microsoft.com/partner/competency/ is vcomp/empower/default.aspx
There may be certain restrictions, but it appears that it is actually the case where it's possible to get the MSDN Universal subscription(s) for $375 (that's yearly though) through this program.
Actually, it accepts external requests but rejects them with a 403 forbidden message. Would be nicer if it didn't even bind to port 80 on external IPs at all if they're going to make that claim.
This was in the previous VS.NET 2005 though...not this latest one.
you should feel bad....I believe MSDN Universal is only around $375 for one license which will get you VS.NET Enterprise Architect, Professional, and standard. That's 3 licenses for $375...one more MSDN Universal and you're ready to go with one license to spare.
You really should look into.NET. It's not Microsoft's trend of the week....it is definately the New Way Of Doing Things (tm) in the Windows world. I could go into more evidence of this, but you'd be better of researching it yourself.
Shouldn't be too bad. All the new code-behind model does is take all the RAD wired events and properties that were in the same source file as all your code and put them in a seperate source file. This was one of the purposes of the new "partial classes" feature of.NET 2.0.
True. They have begun to address that though. They've included a Nant like build system called "msbuild". They're also releasing a new (and supposedly greatly improved) version of the disgrace that is Visual SourceSafe.
Well, all the apps which are backed by SQL databases are crashing all over the place. After its several years in the field now SQL has been proven to be unstable, unreliable, and completely incapable of doing the job.
Evidence of this is in the hundreds of companies who are completely unable to maintain a database of any significant size despite vendor claims to the contrary. Also, note the thousands of websites which routinely fail due to random database problems. It appears that all SQL products are sad implementations of a horrible standard which simply does not cut it.
Then there's no point.....Microsoft isn't trying to market their development kit to you (essentially a hobbyiest)...they're trying to market the kit to professionals and businesses.
Sorry, I was a little aggrivated when reading this thread...I guess I didn't realize how easy it is to come off as hostile, especially when your post really wasn't of the condescending tone as the others in this thread (including mine).
Lets see...where ELSE was it explained in this thread.... (please try to understand, if you can, this is not dictionary terms but the definition of these terms in relation to software engineering...)
defect: a problem in the software's behavior that has been found
bug: same as a defect but has not been found.
Now, if you can take this in context of what the guy was saying in his MSDN blog...A release free from defects may still contain problems, but these problems have not been found.
Can you accept that MAYBE just MAYBE there is use in the world for these two terms to have different meanings in this context? Is that so hard?
Why can't you get it that a defect and a bug are different things? Is your blind desire to bash Microsoft so strong that you can't fathom that two terms can be similar but not exactly the same?
I'm not in graphics design in any way, but my guess would be that for fat fonts (that you find in most terminals), white on black is more pleasing to the eyes than thin fonts (as you find on most webpages).
From an end user stand point IPv6 will not change DNS....I believe that's what he means when he says "web addresses". Going from remembering phone numbers to IP addresses wouldn't be very smart would it?
The grandparent who suggested that we will speak a person's fullname to reach them hasn't thought through that idea very much. A DNS-like system makes more sense. Allows for people to not be in the public directory but still be reachable for one thing.
The "speak the name of the person you want to call into the phone" idea would really be too tedious.
Essentially your phone would probably have a buddy list and a directory for searching, possibly using voice commands...
Slashdot Mirror
What freedom is being restricted? Calls can still be made to those countries, so what exactly is the problem?
The latest version of the CLR brings 64bit compatability. As for companies jumping ship, I've heard some of both (jumping on and off that is)...but neither of what your or I hear is really valid as far as looking at the entire landscape.....only time will tell.
Damnit...sorry about the lack of hyperlinks
l
s vcomp/empower/default.aspx
http://www.joelonsoftware.com/articles/APIWar.htm
http://members.microsoft.com/partner/competency/i
This offer is for companies only however...so my original reply is probably not valid as I doubt you could register one company twice in this program.
Wow, I actually managed to find where I got that number from....
t ml
/ is vcomp/empower/default.aspx
http://www.joelonsoftware.com/articles/APIWar.h
(search for 375 and you'll see the part where he mentions it)
http://members.microsoft.com/partner/competency
There may be certain restrictions, but it appears that it is actually the case where it's possible to get the MSDN Universal subscription(s) for $375 (that's yearly though) through this program.
VS 2005 beta does cover Avalon/XAML development. Don't know about the express versions.
Though, I believe you need to be running longhorn to be able to actually run an Avalon/XAML app.
Actually, it accepts external requests but rejects them with a 403 forbidden message. Would be nicer if it didn't even bind to port 80 on external IPs at all if they're going to make that claim.
This was in the previous VS.NET 2005 though...not this latest one.
you should feel bad....I believe MSDN Universal is only around $375 for one license which will get you VS.NET Enterprise Architect, Professional, and standard. That's 3 licenses for $375...one more MSDN Universal and you're ready to go with one license to spare.
You really should look into .NET. It's not Microsoft's trend of the week....it is definately the New Way Of Doing Things (tm) in the Windows world. I could go into more evidence of this, but you'd be better of researching it yourself.
Shouldn't be too bad. All the new code-behind model does is take all the RAD wired events and properties that were in the same source file as all your code and put them in a seperate source file. This was one of the purposes of the new "partial classes" feature of .NET 2.0.
True. They have begun to address that though. They've included a Nant like build system called "msbuild". They're also releasing a new (and supposedly greatly improved) version of the disgrace that is Visual SourceSafe.
Haha...=-P That was my intention...=)
Strange how you made the same typo I did... "entire" instead of "entirely".
Haha....I thought the sarcasm was pretty obvious from the get go...but then again I'm usually the only one who can detect my sarcasm, heh.
Well, all the apps which are backed by SQL databases are crashing all over the place. After its several years in the field now SQL has been proven to be unstable, unreliable, and completely incapable of doing the job.
.
Evidence of this is in the hundreds of companies who are completely unable to maintain a database of any significant size despite vendor claims to the contrary. Also, note the thousands of websites which routinely fail due to random database problems. It appears that all SQL products are sad implementations of a horrible standard which simply does not cut it
(the above is intended entire as sarcasm)
3D porn is just too good to be true. It sure would be nice to be able to change some of those retarded camera angles though.
Hey! At least you don't have to worry about your site getting hacked for the answers!
Then there's no point.....Microsoft isn't trying to market their development kit to you (essentially a hobbyiest)...they're trying to market the kit to professionals and businesses.
What is there to complain about?
Come on! You're asking this on Slashdot!
Sorry, I was a little aggrivated when reading this thread...I guess I didn't realize how easy it is to come off as hostile, especially when your post really wasn't of the condescending tone as the others in this thread (including mine).
I apologize.
Ironic....I ignored his sig until you mentioned it. Now I'm checking out the site.
=)
Lets see...where ELSE was it explained in this thread.... (please try to understand, if you can, this is not dictionary terms but the definition of these terms in relation to software engineering...)
defect: a problem in the software's behavior that has been found
bug: same as a defect but has not been found.
Now, if you can take this in context of what the guy was saying in his MSDN blog...A release free from defects may still contain problems, but these problems have not been found.
Can you accept that MAYBE just MAYBE there is use in the world for these two terms to have different meanings in this context? Is that so hard?
Why can't you get it that a defect and a bug are different things? Is your blind desire to bash Microsoft so strong that you can't fathom that two terms can be similar but not exactly the same?
I'm not in graphics design in any way, but my guess would be that for fat fonts (that you find in most terminals), white on black is more pleasing to the eyes than thin fonts (as you find on most webpages).
From an end user stand point IPv6 will not change DNS....I believe that's what he means when he says "web addresses". Going from remembering phone numbers to IP addresses wouldn't be very smart would it?
Umm....isn't that how phones worked before we developed the useful phone switches and phone-number system?
Someone mod the parent up.....
The grandparent who suggested that we will speak a person's fullname to reach them hasn't thought through that idea very much. A DNS-like system makes more sense. Allows for people to not be in the public directory but still be reachable for one thing.
The "speak the name of the person you want to call into the phone" idea would really be too tedious.
Essentially your phone would probably have a buddy list and a directory for searching, possibly using voice commands...