Oh My God , Not again ! Whidbey Delay

it seems that Yukon and Whidbey are shifted again(!!!!) up till first half 2005.
I guess it's good to have a heavily tested product but come on it became endless.
so what do you think guys.
check it out at :
http://www.eweek.com/article2/0,1759,1546150,00.asp
ByeI'm happy that the product will be well tested and "rock-solid" when it ships.

I am sad, because I was holding off on some redesign of a couple of webpages because I really wanted Master Pages and a few other things.

Well, it will keep me employed, as I will rewrite the pages once Whidbey comes out so I can take advantage of all of the cool stuff in it.

Richard
Even if they come out at the same time, it's going to take more time to migrate db's over from 2000 to Yukon. That's a big ticket item to sell, as companies tend to be very serious and cautious about moving DB's around -- as well they should be.

And Whidbey is already pretty solid.

The real issue here is that a lot people think it's silly to tie Whidbey to Yukon, myself included.

The point here is that so much is rolled up into Whidbey that has absolutely nothing to do with Yukon, that it's absurd to wait until Yukon is finished.
That'll be no good for me because my MSDN subscription ends early next year (assuming the next VS.net would be available to MSDN subscribers). What's the use of having a subscription if you don't get any real software updates? I'll be bummed if it comes out a short time after my subscription ends :(

Then again I expected this to happen so I wouldn't be suprised if it gets pushed back to the summer or fall of 2005. MS products always seem to come out 1 year after they were supposed to come out...
I am implementing some features in Widbey myself. :-)
I am already seriously tempted to use Whidbey for any internal projects. I run a small consulting company and it makes for a nice "proving ground." I am considering building my company website with it. :)

However, releasing anything Whidbey related to a client would be out of the question. It's a shame about the delay. There's so many great things in ASP.NET 2.0.
Ok guys,
how about this, why don't they split the launch for the two products I mean that they said that the delay was because of the CLR integration into Yukon and some issues related to that.So, since Whidbey is still on the same old schedule "last quarter of 2004",and the delay is from the Yukon side,release the Whidbey and make another launch event for Yukon ,
but I guess they are waiting to launch the products in one day which seems to be very reasonable from commercial point of view,
see, they will save the cost of the launch event :) .
The current Alpha ASP.NET an Whidbey are already worth the progress. My feeling is that it is already more stable than Visual Studio 2002 ever was.

Why not release Whidbey, and do SP1 together with Yukon?

Well I gues this discussion has (and might still be) gone on inside Microsoft. Stick to the old schedule for Whidbey!

OK. Again...How to handle single quotes in SQL Strings? ASP.NET/ADO.NET

How can I handle the user entering single quotes like in
Bob's mini mart?
If I use command objects will this no longer be an issue?
I guess that would mean no simple adhoc SQL statements right?
like SELECT name from WHATEVER
would need a command object with
"SELECT @dotnet.itags.org.NAME, etc.
and then params
is this the way to solve the problem?
Thanks,
ShaneUse command objects. The single quote "problem" will go away.
Don't use ad-hoc SQL statements that are concatenated from user input. You
are leaving your application vulnerable to a SQL injection attack.
Colin
"SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
news:OzRbcimSEHA.3636@.TK2MSFTNGP09.phx.gbl...
> How can I handle the user entering single quotes like in
> Bob's mini mart?
> If I use command objects will this no longer be an issue?
> I guess that would mean no simple adhoc SQL statements right?
> like SELECT name from WHATEVER
> would need a command object with
> "SELECT @.NAME, etc.
> and then params
> is this the way to solve the problem?
> Thanks,
> Shane
>
>
Yes, use parameter objects.
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net
"SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
news:OzRbcimSEHA.3636@.TK2MSFTNGP09.phx.gbl...
> How can I handle the user entering single quotes like in
> Bob's mini mart?
> If I use command objects will this no longer be an issue?
> I guess that would mean no simple adhoc SQL statements right?
> like SELECT name from WHATEVER
> would need a command object with
> "SELECT @.NAME, etc.
> and then params
> is this the way to solve the problem?
> Thanks,
> Shane
>
>
OK. That is what I had thought.
So to do that in command ojbects I do something like.
dim cmd as new sqlCommand("SELECT Name,Address,City FROM tblPerson WHERE
State=@.State",conn)
is that right? And then just add @.State as a param?
I don't need to do the same for the output params right? LIke Name, Address
and City--or do I have to do them the same?
Shane
"Steve C. Orr [MVP, MCSD]" <Steve@.Orr.net> wrote in message
news:Og3zd2sSEHA.1168@.TK2MSFTNGP11.phx.gbl...
> Yes, use parameter objects.
> --
> I hope this helps,
> Steve C. Orr, MCSD, MVP
> http://Steve.Orr.net
>
> "SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
> news:OzRbcimSEHA.3636@.TK2MSFTNGP09.phx.gbl...
>
Basically correct.
Output parameters would need to be declared, but in your example, you
seem to be returning a recordset, not output parameters. This would
return a .NET dataset with multiple records which you could either
bind to an ASP control or use in whatever method you deem prudent :)
On Sun, 6 Jun 2004 09:49:15 -0500, "SStory"
<TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote:

>OK. That is what I had thought.
>So to do that in command ojbects I do something like.
>dim cmd as new sqlCommand("SELECT Name,Address,City FROM tblPerson WHERE
>State=@.State",conn)
>is that right? And then just add @.State as a param?
>I don't need to do the same for the output params right? LIke Name, Addres
s
>and City--or do I have to do them the same?
>Shane
>
>"Steve C. Orr [MVP, MCSD]" <Steve@.Orr.net> wrote in message
>news:Og3zd2sSEHA.1168@.TK2MSFTNGP11.phx.gbl...
>
Thanks Dan,
Will try to go through and fix offending code.
Shane
"Dan Brussee" <dbrussee@.nc.rr.com> wrote in message
news:7ve6c0ls13v3k00iu79pbdf20ggd73m8tp@.
4ax.com...
> Basically correct.
> Output parameters would need to be declared, but in your example, you
> seem to be returning a recordset, not output parameters. This would
> return a .NET dataset with multiple records which you could either
> bind to an ASP control or use in whatever method you deem prudent :)
>
> On Sun, 6 Jun 2004 09:49:15 -0500, "SStory"
> <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote:
>
Address
>

OK. Again...How to handle single quotes in SQL Strings? ASP.NET/ADO.NET

How can I handle the user entering single quotes like in

Bob's mini mart?

If I use command objects will this no longer be an issue?

I guess that would mean no simple adhoc SQL statements right?

like SELECT name from WHATEVER

would need a command object with

"SELECT @dotnet.itags.org.NAME, etc.
and then params

is this the way to solve the problem?

Thanks,

ShaneUse command objects. The single quote "problem" will go away.

Don't use ad-hoc SQL statements that are concatenated from user input. You
are leaving your application vulnerable to a SQL injection attack.

Colin

"SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
news:OzRbcimSEHA.3636@.TK2MSFTNGP09.phx.gbl...
> How can I handle the user entering single quotes like in
> Bob's mini mart?
> If I use command objects will this no longer be an issue?
> I guess that would mean no simple adhoc SQL statements right?
> like SELECT name from WHATEVER
> would need a command object with
> "SELECT @.NAME, etc.
> and then params
> is this the way to solve the problem?
> Thanks,
> Shane
Yes, use parameter objects.

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net

"SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
news:OzRbcimSEHA.3636@.TK2MSFTNGP09.phx.gbl...
> How can I handle the user entering single quotes like in
> Bob's mini mart?
> If I use command objects will this no longer be an issue?
> I guess that would mean no simple adhoc SQL statements right?
> like SELECT name from WHATEVER
> would need a command object with
> "SELECT @.NAME, etc.
> and then params
> is this the way to solve the problem?
> Thanks,
> Shane
OK. That is what I had thought.

So to do that in command ojbects I do something like.

dim cmd as new sqlCommand("SELECT Name,Address,City FROM tblPerson WHERE
State=@.State",conn)

is that right? And then just add @.State as a param?

I don't need to do the same for the output params right? LIke Name, Address
and City--or do I have to do them the same?

Shane

"Steve C. Orr [MVP, MCSD]" <Steve@.Orr.net> wrote in message
news:Og3zd2sSEHA.1168@.TK2MSFTNGP11.phx.gbl...
> Yes, use parameter objects.
> --
> I hope this helps,
> Steve C. Orr, MCSD, MVP
> http://Steve.Orr.net
>
> "SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
> news:OzRbcimSEHA.3636@.TK2MSFTNGP09.phx.gbl...
> > How can I handle the user entering single quotes like in
> > Bob's mini mart?
> > If I use command objects will this no longer be an issue?
> > I guess that would mean no simple adhoc SQL statements right?
> > like SELECT name from WHATEVER
> > would need a command object with
> > "SELECT @.NAME, etc.
> > and then params
> > is this the way to solve the problem?
> > Thanks,
> > Shane
Basically correct.

Output parameters would need to be declared, but in your example, you
seem to be returning a recordset, not output parameters. This would
return a .NET dataset with multiple records which you could either
bind to an ASP control or use in whatever method you deem prudent :)

On Sun, 6 Jun 2004 09:49:15 -0500, "SStory"
<TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote:

>OK. That is what I had thought.
>So to do that in command ojbects I do something like.
>dim cmd as new sqlCommand("SELECT Name,Address,City FROM tblPerson WHERE
>State=@.State",conn)
>is that right? And then just add @.State as a param?
>I don't need to do the same for the output params right? LIke Name, Address
>and City--or do I have to do them the same?
>Shane
>
>"Steve C. Orr [MVP, MCSD]" <Steve@.Orr.net> wrote in message
>news:Og3zd2sSEHA.1168@.TK2MSFTNGP11.phx.gbl...
>> Yes, use parameter objects.
>>
>> --
>> I hope this helps,
>> Steve C. Orr, MCSD, MVP
>> http://Steve.Orr.net
>>
>>
>> "SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
>> news:OzRbcimSEHA.3636@.TK2MSFTNGP09.phx.gbl...
>> > How can I handle the user entering single quotes like in
>>> > Bob's mini mart?
>>> > If I use command objects will this no longer be an issue?
>>> > I guess that would mean no simple adhoc SQL statements right?
>>> > like SELECT name from WHATEVER
>>> > would need a command object with
>>> > "SELECT @.NAME, etc.
>> > and then params
>>> > is this the way to solve the problem?
>>> > Thanks,
>>> > Shane
>>>>>
>
Thanks Dan,

Will try to go through and fix offending code.

Shane

"Dan Brussee" <dbrussee@.nc.rr.com> wrote in message
news:7ve6c0ls13v3k00iu79pbdf20ggd73m8tp@.4ax.com...
> Basically correct.
> Output parameters would need to be declared, but in your example, you
> seem to be returning a recordset, not output parameters. This would
> return a .NET dataset with multiple records which you could either
> bind to an ASP control or use in whatever method you deem prudent :)
>
> On Sun, 6 Jun 2004 09:49:15 -0500, "SStory"
> <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote:
> >OK. That is what I had thought.
> >So to do that in command ojbects I do something like.
> >dim cmd as new sqlCommand("SELECT Name,Address,City FROM tblPerson WHERE
> >State=@.State",conn)
> >is that right? And then just add @.State as a param?
> >I don't need to do the same for the output params right? LIke Name,
Address
> >and City--or do I have to do them the same?
> >Shane
> >"Steve C. Orr [MVP, MCSD]" <Steve@.Orr.net> wrote in message
> >news:Og3zd2sSEHA.1168@.TK2MSFTNGP11.phx.gbl...
> >> Yes, use parameter objects.
> >>
> >> --
> >> I hope this helps,
> >> Steve C. Orr, MCSD, MVP
> >> http://Steve.Orr.net
> >>
> >>
> >> "SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
> >> news:OzRbcimSEHA.3636@.TK2MSFTNGP09.phx.gbl...
> >> > How can I handle the user entering single quotes like in
> >> >> > Bob's mini mart?
> >> >> > If I use command objects will this no longer be an issue?
> >> >> > I guess that would mean no simple adhoc SQL statements right?
> >> >> > like SELECT name from WHATEVER
> >> >> > would need a command object with
> >> >> > "SELECT @.NAME, etc.
> >> > and then params
> >> >> > is this the way to solve the problem?
> >> >> > Thanks,
> >> >> > Shane
> >> >> >> >>
> >