I would like to share my disappointment of Microsoft with you readers. Be
aware that I'm in no way a Microsoft "basher" and that, in fact, I use their
programming technologies everyday. More importantly, I find these
technologies quite useful and, most of the time, very well done.
But I'm currently quite fed up with what Microsoft is doing with the next
generation of the .NET Framework. It has absolutely nothing to do with the
functionalities, far from that! It seems like a terrific new product. The
..NET runtime environnement really impressed me from the start and it will
continue to. But the problem here is that MSDN, and all the ressources at
Microsoft, seems to focus on a product that is not out yet.
On MSDN, the majority of articles seems to be "how to do that on Whidbey",
"How Whidbey is great for that", "How life is wonderful with Whidbey", and
bla bla bla. But hey guys, the majority of your readers can't even test the
little example you put in your great articles about Whidbey! Why should I
care? Out there we only have the .NET Framework 1.1 to work with. There's
not even a beta version of whidbey that I can use to experiment with this
great new environnement! Why focus on a product that is not out yet and,
from certains informations, will not even be in the current year!
I was a very "patriotic" reader of MSDN for the great number of quality
article that it propose. But now, I just go there from time to time to
realize, each time, that they talks about something I can't use and will not
be able to use for the next year or so. Imagine a computer hardware magazine
that do mainly reviews of product that readers will never be able to use
before one or two years? I want programming information that is useful for
me now, not hypothetically in the future...
Etienne
34  1521 
Hi Etienne,
You inspired me to blog, you can check out my comments and find out what others in the .NET community have to say at http://weblogs.asp.net/mhawley/archi...14/113085.aspx
Matt Hawley, MCAD .NET http://www.eworldui.net
I would like to share my disappointment of Microsoft with you readers. Be
aware that I'm in no way a Microsoft "basher" and that, in fact, I use their
programming technologies everyday. More importantly, I find these
technologies quite useful and, most of the time, very well done.
But I'm currently quite fed up with what Microsoft is doing with the next
generation of the .NET Framework. It has absolutely nothing to do with the
functionalities, far from that! It seems like a terrific new product. The
.NET runtime environnement really impressed me from the start and it will
continue to. But the problem here is that MSDN, and all the ressources at
Microsoft, seems to focus on a product that is not out yet.
On MSDN, the majority of articles seems to be "how to do that on Whidbey",
"How Whidbey is great for that", "How life is wonderful with Whidbey", and
bla bla bla. But hey guys, the majority of your readers can't even test the
little example you put in your great articles about Whidbey! Why should I
care? Out there we only have the .NET Framework 1.1 to work with. There's
not even a beta version of whidbey that I can use to experiment with this
great new environnement! Why focus on a product that is not out yet and,
from certains informations, will not even be in the current year!
I was a very "patriotic" reader of MSDN for the great number of quality
article that it propose. But now, I just go there from time to time to
realize, each time, that they talks about something I can't use and will not
be able to use for the next year or so. Imagine a computer hardware magazine
that do mainly reviews of product that readers will never be able to use
before one or two years? I want programming information that is useful for
me now, not hypothetically in the future...
Etienne
Hi Etienne,
You inspired me to blog, you can check out my comments and find out what others in the .NET community have to say at http://weblogs.asp.net/mhawley/archi...14/113085.aspx
Matt Hawley, MCAD .NET http://www.eworldui.net
I would like to share my disappointment of Microsoft with you readers. Be
aware that I'm in no way a Microsoft "basher" and that, in fact, I use their
programming technologies everyday. More importantly, I find these
technologies quite useful and, most of the time, very well done.
But I'm currently quite fed up with what Microsoft is doing with the next
generation of the .NET Framework. It has absolutely nothing to do with the
functionalities, far from that! It seems like a terrific new product. The
.NET runtime environnement really impressed me from the start and it will
continue to. But the problem here is that MSDN, and all the ressources at
Microsoft, seems to focus on a product that is not out yet.
On MSDN, the majority of articles seems to be "how to do that on Whidbey",
"How Whidbey is great for that", "How life is wonderful with Whidbey", and
bla bla bla. But hey guys, the majority of your readers can't even test the
little example you put in your great articles about Whidbey! Why should I
care? Out there we only have the .NET Framework 1.1 to work with. There's
not even a beta version of whidbey that I can use to experiment with this
great new environnement! Why focus on a product that is not out yet and,
from certains informations, will not even be in the current year!
I was a very "patriotic" reader of MSDN for the great number of quality
article that it propose. But now, I just go there from time to time to
realize, each time, that they talks about something I can't use and will not
be able to use for the next year or so. Imagine a computer hardware magazine
that do mainly reviews of product that readers will never be able to use
before one or two years? I want programming information that is useful for
me now, not hypothetically in the future...
Etienne
In article <uk**************@TK2MSFTNGP09.phx.gbl>, Matt Hawley wrote: Hi Etienne,
You inspired me to blog, you can check out my comments and find out
what others in the .NET community have to say at
http://weblogs.asp.net/mhawley/archi...14/113085.aspx
And this post inspired me to say that one's blog addvertisement
without any useful text has a very little value to me.
In article <uk**************@TK2MSFTNGP09.phx.gbl>, Matt Hawley wrote: Hi Etienne,
You inspired me to blog, you can check out my comments and find out
what others in the .NET community have to say at
http://weblogs.asp.net/mhawley/archi...14/113085.aspx
And this post inspired me to say that one's blog addvertisement
without any useful text has a very little value to me.
I believe there's a tech preview of Whidbey on the MSDN subscribers download
site, it became available late March. This is a later version to that given
out at the PDC.
We've downloaded it but I haven't installed it yet, so can't comment on it.
(Hopefully it will be a little more stable than the PDC build). Note it is
two or three gigs in size.
Stu
"Etienne Fortin" <so*****@microsoft.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl... I would like to share my disappointment of Microsoft with you readers. Be
aware that I'm in no way a Microsoft "basher" and that, in fact, I use
their programming technologies everyday. More importantly, I find these
technologies quite useful and, most of the time, very well done.
But I'm currently quite fed up with what Microsoft is doing with the next
generation of the .NET Framework. It has absolutely nothing to do with the
functionalities, far from that! It seems like a terrific new product. The
.NET runtime environnement really impressed me from the start and it will
continue to. But the problem here is that MSDN, and all the ressources at
Microsoft, seems to focus on a product that is not out yet.
On MSDN, the majority of articles seems to be "how to do that on Whidbey",
"How Whidbey is great for that", "How life is wonderful with Whidbey", and
bla bla bla. But hey guys, the majority of your readers can't even test
the little example you put in your great articles about Whidbey! Why should I
care? Out there we only have the .NET Framework 1.1 to work with. There's
not even a beta version of whidbey that I can use to experiment with this
great new environnement! Why focus on a product that is not out yet and,
from certains informations, will not even be in the current year!
I was a very "patriotic" reader of MSDN for the great number of quality
article that it propose. But now, I just go there from time to time to
realize, each time, that they talks about something I can't use and will
not be able to use for the next year or so. Imagine a computer hardware
magazine that do mainly reviews of product that readers will never be able to use
before one or two years? I want programming information that is useful for
me now, not hypothetically in the future...
Etienne
I believe there's a tech preview of Whidbey on the MSDN subscribers download
site, it became available late March. This is a later version to that given
out at the PDC.
We've downloaded it but I haven't installed it yet, so can't comment on it.
(Hopefully it will be a little more stable than the PDC build). Note it is
two or three gigs in size.
Stu
"Etienne Fortin" <so*****@microsoft.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl... I would like to share my disappointment of Microsoft with you readers. Be
aware that I'm in no way a Microsoft "basher" and that, in fact, I use
their programming technologies everyday. More importantly, I find these
technologies quite useful and, most of the time, very well done.
But I'm currently quite fed up with what Microsoft is doing with the next
generation of the .NET Framework. It has absolutely nothing to do with the
functionalities, far from that! It seems like a terrific new product. The
.NET runtime environnement really impressed me from the start and it will
continue to. But the problem here is that MSDN, and all the ressources at
Microsoft, seems to focus on a product that is not out yet.
On MSDN, the majority of articles seems to be "how to do that on Whidbey",
"How Whidbey is great for that", "How life is wonderful with Whidbey", and
bla bla bla. But hey guys, the majority of your readers can't even test
the little example you put in your great articles about Whidbey! Why should I
care? Out there we only have the .NET Framework 1.1 to work with. There's
not even a beta version of whidbey that I can use to experiment with this
great new environnement! Why focus on a product that is not out yet and,
from certains informations, will not even be in the current year!
I was a very "patriotic" reader of MSDN for the great number of quality
article that it propose. But now, I just go there from time to time to
realize, each time, that they talks about something I can't use and will
not be able to use for the next year or so. Imagine a computer hardware
magazine that do mainly reviews of product that readers will never be able to use
before one or two years? I want programming information that is useful for
me now, not hypothetically in the future...
Etienne
I AGREE
I'm sick to death of seeing articles about non-existant products .... and so
what if its available on subscriber downloads.
I'll put money on the fact that most MSDN site visitors don't have access to
that.
I'm also sick to death of new .net technology - with 80% of software
projects failing the industry needs more time to adopt and get over the
curve.
-p
"Etienne Fortin" <so*****@microsoft.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl... I would like to share my disappointment of Microsoft with you readers. Be
aware that I'm in no way a Microsoft "basher" and that, in fact, I use
their programming technologies everyday. More importantly, I find these
technologies quite useful and, most of the time, very well done.
But I'm currently quite fed up with what Microsoft is doing with the next
generation of the .NET Framework. It has absolutely nothing to do with the
functionalities, far from that! It seems like a terrific new product. The
.NET runtime environnement really impressed me from the start and it will
continue to. But the problem here is that MSDN, and all the ressources at
Microsoft, seems to focus on a product that is not out yet.
On MSDN, the majority of articles seems to be "how to do that on Whidbey",
"How Whidbey is great for that", "How life is wonderful with Whidbey", and
bla bla bla. But hey guys, the majority of your readers can't even test
the little example you put in your great articles about Whidbey! Why should I
care? Out there we only have the .NET Framework 1.1 to work with. There's
not even a beta version of whidbey that I can use to experiment with this
great new environnement! Why focus on a product that is not out yet and,
from certains informations, will not even be in the current year!
I was a very "patriotic" reader of MSDN for the great number of quality
article that it propose. But now, I just go there from time to time to
realize, each time, that they talks about something I can't use and will
not be able to use for the next year or so. Imagine a computer hardware
magazine that do mainly reviews of product that readers will never be able to use
before one or two years? I want programming information that is useful for
me now, not hypothetically in the future...
Etienne
I AGREE
I'm sick to death of seeing articles about non-existant products .... and so
what if its available on subscriber downloads.
I'll put money on the fact that most MSDN site visitors don't have access to
that.
I'm also sick to death of new .net technology - with 80% of software
projects failing the industry needs more time to adopt and get over the
curve.
-p
"Etienne Fortin" <so*****@microsoft.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl... I would like to share my disappointment of Microsoft with you readers. Be
aware that I'm in no way a Microsoft "basher" and that, in fact, I use
their programming technologies everyday. More importantly, I find these
technologies quite useful and, most of the time, very well done.
But I'm currently quite fed up with what Microsoft is doing with the next
generation of the .NET Framework. It has absolutely nothing to do with the
functionalities, far from that! It seems like a terrific new product. The
.NET runtime environnement really impressed me from the start and it will
continue to. But the problem here is that MSDN, and all the ressources at
Microsoft, seems to focus on a product that is not out yet.
On MSDN, the majority of articles seems to be "how to do that on Whidbey",
"How Whidbey is great for that", "How life is wonderful with Whidbey", and
bla bla bla. But hey guys, the majority of your readers can't even test
the little example you put in your great articles about Whidbey! Why should I
care? Out there we only have the .NET Framework 1.1 to work with. There's
not even a beta version of whidbey that I can use to experiment with this
great new environnement! Why focus on a product that is not out yet and,
from certains informations, will not even be in the current year!
I was a very "patriotic" reader of MSDN for the great number of quality
article that it propose. But now, I just go there from time to time to
realize, each time, that they talks about something I can't use and will
not be able to use for the next year or so. Imagine a computer hardware
magazine that do mainly reviews of product that readers will never be able to use
before one or two years? I want programming information that is useful for
me now, not hypothetically in the future...
Etienne
I just love it when people come to this site and put out crap about how
.NET doesn't work or it's not ready for prime time. Hype is part of
selling any product. So you have to take the good with the bad. They
didn't remove the old articles they only added new ones. If you had gone
to the PDC you would have a copy so maybe the articles are there for the
folks that went to the PDC. I kind of like to plan for the future and
know about what's in the works. It gives me a sense that Microsoft has a
vision and is willing to share it withn us in advance.
IMHO that's a good thing.
Wiz
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
I just love it when people come to this site and put out crap about how
.NET doesn't work or it's not ready for prime time. Hype is part of
selling any product. So you have to take the good with the bad. They
didn't remove the old articles they only added new ones. If you had gone
to the PDC you would have a copy so maybe the articles are there for the
folks that went to the PDC. I kind of like to plan for the future and
know about what's in the works. It gives me a sense that Microsoft has a
vision and is willing to share it withn us in advance.
IMHO that's a good thing.
Wiz
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Posting it all over their site isn't a good thing and I do have a copy
because I'm a subscriber ....
You work on a $2million failed project and then tell me .net rocks ... .net
is good but the developers using it are not! I never said it was bad, I said
the industry needs time to adapt so don't put words in my mouth. The
software industry is dying, wakeup! too many visions, too many "best"
practices, too many damn patterns.
-p
- I feel a flame coming on
"WizyDig" <so*****@microsoft.com> wrote in message
news:ux**************@tk2msftngp13.phx.gbl... I just love it when people come to this site and put out crap about how
NET doesn't work or it's not ready for prime time. Hype is part of
selling any product. So you have to take the good with the bad. They
didn't remove the old articles they only added new ones. If you had gone
to the PDC you would have a copy so maybe the articles are there for the
folks that went to the PDC. I kind of like to plan for the future and
know about what's in the works. It gives me a sense that Microsoft has a
vision and is willing to share it withn us in advance.
IMHO that's a good thing.
Wiz
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Posting it all over their site isn't a good thing and I do have a copy
because I'm a subscriber ....
You work on a $2million failed project and then tell me .net rocks ... .net
is good but the developers using it are not! I never said it was bad, I said
the industry needs time to adapt so don't put words in my mouth. The
software industry is dying, wakeup! too many visions, too many "best"
practices, too many damn patterns.
-p
- I feel a flame coming on
"WizyDig" <so*****@microsoft.com> wrote in message
news:ux**************@tk2msftngp13.phx.gbl... I just love it when people come to this site and put out crap about how
NET doesn't work or it's not ready for prime time. Hype is part of
selling any product. So you have to take the good with the bad. They
didn't remove the old articles they only added new ones. If you had gone
to the PDC you would have a copy so maybe the articles are there for the
folks that went to the PDC. I kind of like to plan for the future and
know about what's in the works. It gives me a sense that Microsoft has a
vision and is willing to share it withn us in advance.
IMHO that's a good thing.
Wiz
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
What caused the project to fail? Try and be specific. Was it a fresh
from scratch project or a conversion? If it was a conversion what was
it converted from. What is a database app if so which dataabse did you
use? If not what did the app do? Was it a browser based
internet/intranet app if so which one. Or was it a windows app?
Wiz
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
What caused the project to fail? Try and be specific. Was it a fresh
from scratch project or a conversion? If it was a conversion what was
it converted from. What is a database app if so which dataabse did you
use? If not what did the app do? Was it a browser based
internet/intranet app if so which one. Or was it a windows app?
Wiz
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Slightly off topic, but are the new features going to be sensibly documented
in the help files? Or are we just going to be subjected to another batch of
"here, this is the code to use if you want to do exactly what this example
does" type garbage?
"Etienne Fortin" <so*****@microsoft.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl... I would like to share my disappointment of Microsoft with you readers. Be
aware that I'm in no way a Microsoft "basher" and that, in fact, I use
their programming technologies everyday. More importantly, I find these
technologies quite useful and, most of the time, very well done.
But I'm currently quite fed up with what Microsoft is doing with the next
generation of the .NET Framework. It has absolutely nothing to do with the
functionalities, far from that! It seems like a terrific new product. The
.NET runtime environnement really impressed me from the start and it will
continue to. But the problem here is that MSDN, and all the ressources at
Microsoft, seems to focus on a product that is not out yet.
On MSDN, the majority of articles seems to be "how to do that on Whidbey",
"How Whidbey is great for that", "How life is wonderful with Whidbey", and
bla bla bla. But hey guys, the majority of your readers can't even test
the little example you put in your great articles about Whidbey! Why should I
care? Out there we only have the .NET Framework 1.1 to work with. There's
not even a beta version of whidbey that I can use to experiment with this
great new environnement! Why focus on a product that is not out yet and,
from certains informations, will not even be in the current year!
I was a very "patriotic" reader of MSDN for the great number of quality
article that it propose. But now, I just go there from time to time to
realize, each time, that they talks about something I can't use and will
not be able to use for the next year or so. Imagine a computer hardware
magazine that do mainly reviews of product that readers will never be able to use
before one or two years? I want programming information that is useful for
me now, not hypothetically in the future...
Etienne
Slightly off topic, but are the new features going to be sensibly documented
in the help files? Or are we just going to be subjected to another batch of
"here, this is the code to use if you want to do exactly what this example
does" type garbage?
"Etienne Fortin" <so*****@microsoft.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl... I would like to share my disappointment of Microsoft with you readers. Be
aware that I'm in no way a Microsoft "basher" and that, in fact, I use
their programming technologies everyday. More importantly, I find these
technologies quite useful and, most of the time, very well done.
But I'm currently quite fed up with what Microsoft is doing with the next
generation of the .NET Framework. It has absolutely nothing to do with the
functionalities, far from that! It seems like a terrific new product. The
.NET runtime environnement really impressed me from the start and it will
continue to. But the problem here is that MSDN, and all the ressources at
Microsoft, seems to focus on a product that is not out yet.
On MSDN, the majority of articles seems to be "how to do that on Whidbey",
"How Whidbey is great for that", "How life is wonderful with Whidbey", and
bla bla bla. But hey guys, the majority of your readers can't even test
the little example you put in your great articles about Whidbey! Why should I
care? Out there we only have the .NET Framework 1.1 to work with. There's
not even a beta version of whidbey that I can use to experiment with this
great new environnement! Why focus on a product that is not out yet and,
from certains informations, will not even be in the current year!
I was a very "patriotic" reader of MSDN for the great number of quality
article that it propose. But now, I just go there from time to time to
realize, each time, that they talks about something I can't use and will
not be able to use for the next year or so. Imagine a computer hardware
magazine that do mainly reviews of product that readers will never be able to use
before one or two years? I want programming information that is useful for
me now, not hypothetically in the future...
Etienne
I'm not allowed to post too much information about it on the .net but I'll
tell you this;
It was in .NET (C#) from scratch and was heavily over engineered. Too many
people read too many books on how to write ENTERPRISE applications and we
ended up with something so generic and abstract that nothing worked and
entropy killed it before they could finish it. Now you could say this wasn't
..NETs fault and I'd agree.
-p
"WizyDig" <so*****@microsoft.com> wrote in message
news:OW**************@TK2MSFTNGP11.phx.gbl... What caused the project to fail? Try and be specific. Was it a fresh
from scratch project or a conversion? If it was a conversion what was
it converted from. What is a database app if so which dataabse did you
use? If not what did the app do? Was it a browser based
internet/intranet app if so which one. Or was it a windows app?
Wiz
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
I'm not allowed to post too much information about it on the .net but I'll
tell you this;
It was in .NET (C#) from scratch and was heavily over engineered. Too many
people read too many books on how to write ENTERPRISE applications and we
ended up with something so generic and abstract that nothing worked and
entropy killed it before they could finish it. Now you could say this wasn't
..NETs fault and I'd agree.
-p
"WizyDig" <so*****@microsoft.com> wrote in message
news:OW**************@TK2MSFTNGP11.phx.gbl... What caused the project to fail? Try and be specific. Was it a fresh
from scratch project or a conversion? If it was a conversion what was
it converted from. What is a database app if so which dataabse did you
use? If not what did the app do? Was it a browser based
internet/intranet app if so which one. Or was it a windows app?
Wiz
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it! It was in .NET (C#) from scratch and was heavily over engineered. Too many
people read too many books on how to write ENTERPRISE applications and we
ended up with something so generic and abstract that nothing worked and
entropy killed it before they could finish it. Now you could say this
wasn't .NETs fault and I'd agree.
It wasn't. (VS).Net is nothing more than a (wonderful) *tool*.
It depends on you how to use it.
--
Miha Markic [MVP C#] - RightHand .NET consulting & software development
miha at rthand com www.rthand.com It was in .NET (C#) from scratch and was heavily over engineered. Too many
people read too many books on how to write ENTERPRISE applications and we
ended up with something so generic and abstract that nothing worked and
entropy killed it before they could finish it. Now you could say this
wasn't .NETs fault and I'd agree.
It wasn't. (VS).Net is nothing more than a (wonderful) *tool*.
It depends on you how to use it.
--
Miha Markic [MVP C#] - RightHand .NET consulting & software development
miha at rthand com www.rthand.com
>But I'm currently quite fed up with what Microsoft is doing with the next generation of the .NET Framework. It has absolutely nothing to do with the
functionalities, far from that! It seems like a terrific new product.
Oh, c'mon - if they were *NOT* telling you anything, you'd be bashing
them for being secretive and not letting you know what's coming in the
next few months !!
Be glad, and thankful, for the amount of early information that
Microsoft is providing! I'm very glad they do!!
MArc
>But I'm currently quite fed up with what Microsoft is doing with the next generation of the .NET Framework. It has absolutely nothing to do with the
functionalities, far from that! It seems like a terrific new product.
Oh, c'mon - if they were *NOT* telling you anything, you'd be bashing
them for being secretive and not letting you know what's coming in the
next few months !!
Be glad, and thankful, for the amount of early information that
Microsoft is providing! I'm very glad they do!!
MArc
I'm glad but what about articles on stuff we can use TODAY?
They have sections for things like whidbey .....
-p
"Marc Scheuner [MVP ADSI]" <m.********@inova.SPAMBEGONE.ch> wrote in message
news:fu********************************@4ax.com... But I'm currently quite fed up with what Microsoft is doing with the next
generation of the .NET Framework. It has absolutely nothing to do with
thefunctionalities, far from that! It seems like a terrific new product.
Oh, c'mon - if they were *NOT* telling you anything, you'd be bashing
them for being secretive and not letting you know what's coming in the
next few months !!
Be glad, and thankful, for the amount of early information that
Microsoft is providing! I'm very glad they do!!
MArc
I'm glad but what about articles on stuff we can use TODAY?
They have sections for things like whidbey .....
-p
"Marc Scheuner [MVP ADSI]" <m.********@inova.SPAMBEGONE.ch> wrote in message
news:fu********************************@4ax.com... But I'm currently quite fed up with what Microsoft is doing with the next
generation of the .NET Framework. It has absolutely nothing to do with
thefunctionalities, far from that! It seems like a terrific new product.
Oh, c'mon - if they were *NOT* telling you anything, you'd be bashing
them for being secretive and not letting you know what's coming in the
next few months !!
Be glad, and thankful, for the amount of early information that
Microsoft is providing! I'm very glad they do!!
MArc
Sorry, but I don't mind for some inside informations. But delivering tons of
articles on technology that we can't even look at, it's not useful. They can
have article on new features, new functionalities, but what's the point,
years before release, to have very specific and detailed articles on how to
do that, and that, and that with the new runtime? There's absolutely no
point of doing it since it's not useful for anyone.
"Marc Scheuner [MVP ADSI]" <m.********@inova.SPAMBEGONE.ch> wrote in message
news:fu********************************@4ax.com... But I'm currently quite fed up with what Microsoft is doing with the next
generation of the .NET Framework. It has absolutely nothing to do with
thefunctionalities, far from that! It seems like a terrific new product.
Oh, c'mon - if they were *NOT* telling you anything, you'd be bashing
them for being secretive and not letting you know what's coming in the
next few months !!
Be glad, and thankful, for the amount of early information that
Microsoft is providing! I'm very glad they do!!
MArc
Sorry, but I don't mind for some inside informations. But delivering tons of
articles on technology that we can't even look at, it's not useful. They can
have article on new features, new functionalities, but what's the point,
years before release, to have very specific and detailed articles on how to
do that, and that, and that with the new runtime? There's absolutely no
point of doing it since it's not useful for anyone.
"Marc Scheuner [MVP ADSI]" <m.********@inova.SPAMBEGONE.ch> wrote in message
news:fu********************************@4ax.com... But I'm currently quite fed up with what Microsoft is doing with the next
generation of the .NET Framework. It has absolutely nothing to do with
thefunctionalities, far from that! It seems like a terrific new product.
Oh, c'mon - if they were *NOT* telling you anything, you'd be bashing
them for being secretive and not letting you know what's coming in the
next few months !!
Be glad, and thankful, for the amount of early information that
Microsoft is providing! I'm very glad they do!!
MArc
I beg to differ on the usefullness. Its very useful to me and the many other developers out there who do have a copy of Whidbey. Sure, we may be the "special" many that have it (and MS is looking into more ways of getting it out to a broader range of developers each time), but there a re a ton that do, and need resources that they're spitting out so we can be on top of the ball whenever VS.NET 2005 is finally released.
To me, it sounds like a hissy fit that you don't have VS.NET 2005 CTP, or the time/desire to learn about things coming in the future. This is not how I take my career and life, I'm always looking into new products coming out, especially those that I will be using in the future. Its better to know the tool *good enough* prior to its final release so your not caught off gaurd with all its new functionality and usefullness.
That said, get over it. The articles are currently there, and there's nothing you can do about it. MS and other publishers are going to continue to produce pre-release content on VS.NET 2005, Yukon, Longhorn, etc.
Matt Hawley, MCAD .NET http://www.eworldui.net
Sorry, but I don't mind for some inside informations. But delivering tons of
articles on technology that we can't even look at, it's not useful. They can
have article on new features, new functionalities, but what's the point,
years before release, to have very specific and detailed articles on how to
do that, and that, and that with the new runtime? There's absolutely no
point of doing it since it's not useful for anyone.
"Marc Scheuner [MVP ADSI]" <m.********@inova.SPAMBEGONE.ch> wrote in message
news:fu********************************@4ax.com... But I'm currently quite fed up with what Microsoft is doing with the next
generation of the .NET Framework. It has absolutely nothing to do with
thefunctionalities, far from that! It seems like a terrific new product.
Oh, c'mon - if they were *NOT* telling you anything, you'd be bashing
them for being secretive and not letting you know what's coming in the
next few months !!
Be glad, and thankful, for the amount of early information that
Microsoft is providing! I'm very glad they do!!
MArc
I beg to differ on the usefullness. Its very useful to me and the many other developers out there who do have a copy of Whidbey. Sure, we may be the "special" many that have it (and MS is looking into more ways of getting it out to a broader range of developers each time), but there a re a ton that do, and need resources that they're spitting out so we can be on top of the ball whenever VS.NET 2005 is finally released.
To me, it sounds like a hissy fit that you don't have VS.NET 2005 CTP, or the time/desire to learn about things coming in the future. This is not how I take my career and life, I'm always looking into new products coming out, especially those that I will be using in the future. Its better to know the tool *good enough* prior to its final release so your not caught off gaurd with all its new functionality and usefullness.
That said, get over it. The articles are currently there, and there's nothing you can do about it. MS and other publishers are going to continue to produce pre-release content on VS.NET 2005, Yukon, Longhorn, etc.
Matt Hawley, MCAD .NET http://www.eworldui.net
Sorry, but I don't mind for some inside informations. But delivering tons of
articles on technology that we can't even look at, it's not useful. They can
have article on new features, new functionalities, but what's the point,
years before release, to have very specific and detailed articles on how to
do that, and that, and that with the new runtime? There's absolutely no
point of doing it since it's not useful for anyone.
"Marc Scheuner [MVP ADSI]" <m.********@inova.SPAMBEGONE.ch> wrote in message
news:fu********************************@4ax.com... But I'm currently quite fed up with what Microsoft is doing with the next
generation of the .NET Framework. It has absolutely nothing to do with
thefunctionalities, far from that! It seems like a terrific new product.
Oh, c'mon - if they were *NOT* telling you anything, you'd be bashing
them for being secretive and not letting you know what's coming in the
next few months !!
Be glad, and thankful, for the amount of early information that
Microsoft is providing! I'm very glad they do!!
MArc
>Sorry, but I don't mind for some inside informations. But delivering tons of articles on technology that we can't even look at, it's not useful.
There's absolutely no point of doing it since it's not useful for anyone.
What about those people like MVP's and MSDN universal subscribers who
are already using the preview versions?
They are in need of knowing how to do things, too - more so than
others, since there are no books and other means of training /
education available just yet!
Marc
>Sorry, but I don't mind for some inside informations. But delivering tons of articles on technology that we can't even look at, it's not useful.
There's absolutely no point of doing it since it's not useful for anyone.
What about those people like MVP's and MSDN universal subscribers who
are already using the preview versions?
They are in need of knowing how to do things, too - more so than
others, since there are no books and other means of training /
education available just yet!
Marc
Agreed so there should be a seperate section JUST for those people.
I have it and I don't agree .....
"Marc Scheuner [MVP ADSI]" <m.********@inova.SPAMBEGONE.ch> wrote in message
news:vc********************************@4ax.com... Sorry, but I don't mind for some inside informations. But delivering tons
ofarticles on technology that we can't even look at, it's not useful.
There's absolutely no point of doing it since it's not useful for anyone.
What about those people like MVP's and MSDN universal subscribers who
are already using the preview versions?
They are in need of knowing how to do things, too - more so than
others, since there are no books and other means of training /
education available just yet!
Marc
There is something we can do, we can sit here and bitch about it.
And as you see from my others posts we have it at our company but its still
a pain to only
see articles about crap that will probably change. The articles are cool but
you can't PRETEND vs 2003 doesn't exist anymore....
Well this is my last post on this, no point carrying on - this is as bad as
talking to linux developers ;)
-p
"Matt Hawley" <mhawley@n!o!s!p!a!m.integrityts.com> wrote in message
news:Ob**************@TK2MSFTNGP12.phx.gbl... I beg to differ on the usefullness. Its very useful to me and the many
other developers out there who do have a copy of Whidbey. Sure, we may be
the "special" many that have it (and MS is looking into more ways of getting
it out to a broader range of developers each time), but there a re a ton
that do, and need resources that they're spitting out so we can be on top of
the ball whenever VS.NET 2005 is finally released.
To me, it sounds like a hissy fit that you don't have VS.NET 2005 CTP, or
the time/desire to learn about things coming in the future. This is not how
I take my career and life, I'm always looking into new products coming out,
especially those that I will be using in the future. Its better to know the
tool *good enough* prior to its final release so your not caught off gaurd
with all its new functionality and usefullness.
That said, get over it. The articles are currently there, and there's
nothing you can do about it. MS and other publishers are going to continue
to produce pre-release content on VS.NET 2005, Yukon, Longhorn, etc.
Matt Hawley, MCAD .NET
http://www.eworldui.net
Sorry, but I don't mind for some inside informations. But delivering
tons of articles on technology that we can't even look at, it's not useful. They
can have article on new features, new functionalities, but what's the point,
years before release, to have very specific and detailed articles on how
to do that, and that, and that with the new runtime? There's absolutely no
point of doing it since it's not useful for anyone.
"Marc Scheuner [MVP ADSI]" <m.********@inova.SPAMBEGONE.ch> wrote in
message news:fu********************************@4ax.com... > >But I'm currently quite fed up with what Microsoft is doing with the
next > >generation of the .NET Framework. It has absolutely nothing to do with the > >functionalities, far from that! It seems like a terrific new product.
>
> Oh, c'mon - if they were *NOT* telling you anything, you'd be bashing
> them for being secretive and not letting you know what's coming in the
> next few months !!
>
> Be glad, and thankful, for the amount of early information that
> Microsoft is providing! I'm very glad they do!!
>
> MArc
Agreed so there should be a seperate section JUST for those people.
I have it and I don't agree .....
"Marc Scheuner [MVP ADSI]" <m.********@inova.SPAMBEGONE.ch> wrote in message
news:vc********************************@4ax.com... Sorry, but I don't mind for some inside informations. But delivering tons
ofarticles on technology that we can't even look at, it's not useful.
There's absolutely no point of doing it since it's not useful for anyone.
What about those people like MVP's and MSDN universal subscribers who
are already using the preview versions?
They are in need of knowing how to do things, too - more so than
others, since there are no books and other means of training /
education available just yet!
Marc
There is something we can do, we can sit here and bitch about it.
And as you see from my others posts we have it at our company but its still
a pain to only
see articles about crap that will probably change. The articles are cool but
you can't PRETEND vs 2003 doesn't exist anymore....
Well this is my last post on this, no point carrying on - this is as bad as
talking to linux developers ;)
-p
"Matt Hawley" <mhawley@n!o!s!p!a!m.integrityts.com> wrote in message
news:Ob**************@TK2MSFTNGP12.phx.gbl... I beg to differ on the usefullness. Its very useful to me and the many
other developers out there who do have a copy of Whidbey. Sure, we may be
the "special" many that have it (and MS is looking into more ways of getting
it out to a broader range of developers each time), but there a re a ton
that do, and need resources that they're spitting out so we can be on top of
the ball whenever VS.NET 2005 is finally released.
To me, it sounds like a hissy fit that you don't have VS.NET 2005 CTP, or
the time/desire to learn about things coming in the future. This is not how
I take my career and life, I'm always looking into new products coming out,
especially those that I will be using in the future. Its better to know the
tool *good enough* prior to its final release so your not caught off gaurd
with all its new functionality and usefullness.
That said, get over it. The articles are currently there, and there's
nothing you can do about it. MS and other publishers are going to continue
to produce pre-release content on VS.NET 2005, Yukon, Longhorn, etc.
Matt Hawley, MCAD .NET
http://www.eworldui.net
Sorry, but I don't mind for some inside informations. But delivering
tons of articles on technology that we can't even look at, it's not useful. They
can have article on new features, new functionalities, but what's the point,
years before release, to have very specific and detailed articles on how
to do that, and that, and that with the new runtime? There's absolutely no
point of doing it since it's not useful for anyone.
"Marc Scheuner [MVP ADSI]" <m.********@inova.SPAMBEGONE.ch> wrote in
message news:fu********************************@4ax.com... > >But I'm currently quite fed up with what Microsoft is doing with the
next > >generation of the .NET Framework. It has absolutely nothing to do with the > >functionalities, far from that! It seems like a terrific new product.
>
> Oh, c'mon - if they were *NOT* telling you anything, you'd be bashing
> them for being secretive and not letting you know what's coming in the
> next few months !!
>
> Be glad, and thankful, for the amount of early information that
> Microsoft is providing! I'm very glad they do!!
>
> MArc
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Etienne Fortin |
last post by:
I would like to share my disappointment of Microsoft with you readers. Be
aware that I'm in no way a Microsoft "basher" and that, in fact, I use their
programming technologies everyday. More...
|
by: Ludwig |
last post by:
Hi,
I'm looking for C# brain teasers (or VB.NET): a little piece of code
that does something special, or where a little error is. Does anyone
has some of these, or links to sites?
Thanks!
|
by: Charles Arthur |
last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
|
by: ryjfgjl |
last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each...
| |
