Technology Previews of Visual Studio "Whidbey"

re: Technology Previews of Visual Studio "Whidbey"

Koji Ishii — Sun, 22 Feb 2004 07:46:00 GMT

This is awesome. I really like MSFT seeking new way to communicate with developers continuously these days, and this is probably one of the best proposal.
I couldn't find details on the Whidbey official site yet, I just wonder when this is going to start. After beta 1 may make more sense, but I wish it starts before beta 1.

re: Technology Previews of Visual Studio "Whidbey"

Thomas Tomiczek — Sun, 22 Feb 2004 09:01:00 GMT

Same here - where was this ever published?

re: Technology Previews of Visual Studio "Whidbey"

Hans Jergen Ohff — Sun, 22 Feb 2004 13:07:00 GMT

Where is the link, and I guess you have to PAY for it anyway via MSDN.

re: Technology Previews of Visual Studio "Whidbey"

Hans Jergen Ohff — Sun, 22 Feb 2004 13:10:00 GMT

Microsoft should do "PUBLIC" builds for feedback, not restricted to MSDN. Sure we can sigh up but not pay no way, pay for daily build, forget it. After all we will be the ones testing it. They should be grateful.

re: Technology Previews of Visual Studio "Whidbey"

Hans Jergen Ohff — Sun, 22 Feb 2004 13:10:00 GMT

How about a Public RAID / PS or whatever via the web for public bug reporting like bugzilla?

re: Technology Previews of Visual Studio "Whidbey"

Dave Rothgery — Sun, 22 Feb 2004 16:38:00 GMT

I think it makes a lot of sense to restrict builds like this (which almost certainly aren't going to have timebombs built in, like a formal public beta would) to MSDN subscribers and _maybe_ people who have a registered license for VS.NET 2003. There's no point in giving a free copy of version 0.995 to someone who has no intention of ever paying for VS.NET.

re: Technology Previews of Visual Studio "Whidbey"

denny — Sun, 22 Feb 2004 17:24:00 GMT

let us give proof of a registerd vs.net 2003 and perhaps a simple "disclaimer & bug" form to register to get it....

I'll be in MSDN soon but I'm starting my private consulting gig.... so I am working to buy my own MSDN and stuff and not use what my soon-to-be-former-employer has paid for....

so right now I runing eval and trial stuff till I get some cash to pay for the membership in "Club Microsoft" :-)

re: Technology Previews of Visual Studio "Whidbey"

Hans Jergen Ohff — Sun, 22 Feb 2004 17:35:00 GMT

They give it away at trade shows strangely enough, I have an early copy of VS.NET so stop being a tard. They can do that then they can do this now, make it timeout like all the other FREE evaluation copies they give out.

So stop trying to be so elitist, it gets you nowhere. I guess you think the non MSDN subscribers dont give value to a platform.

re: Technology Previews of Visual Studio "Whidbey"

Hans Jergen Ohff — Sun, 22 Feb 2004 17:37:00 GMT

I have no intention of paying for it, it will be on networks on day zero. Whats restricting this going to prevent, nothing, hey they may even get feedback that makes it a better product, I guess you dont want that eh.

"Where do you want to go today", I guess yo u want to go nowhere.

Technology Previews of Visual Studio

Michael's Blog — Sun, 22 Feb 2004 21:20:00 GMT

re: Technology Previews of Visual Studio "Whidbey"

beta — Sun, 22 Feb 2004 21:13:00 GMT

Keep an eye on MarkCli's blog because he is the GPM focusing on these community efforts:
http://blogs.msdn.com/markcli/archive/2004/01/15/59202.aspx

I suspect that the restrictions won't be in place to be elitist but to make support less of a nightmare. VS hasn't done anything like this before so it just makes sense to test the process on a small scale first.

Also, there *is* a external bug database but it is currently restricted to registered users. It used to be http://www.betaplace.com, now it's http://www.beta.microsoft.com

re: Technology Previews of Visual Studio "Whidbey"

Jay Bazuzi [MS] — Mon, 23 Feb 2004 02:06:00 GMT

Regarding public a bug database: there is an effort underway in this area, but I don't know much about it. I don't know when it'll happen, or how it'll work. But it definitely fits in with our efforts to be more open with the development community.

Regarding access to the technology previews: I don't know what it's going to be. If I had my way, I would choose weekly drops of the product, including full source & symbols & Source Control change history.

Regarding mudslinging: please don't do it. This is my blog, but I'm going to avoid censoring any comments if I can. I hope that you can act mature here. In your blog, however, you're welcome to say whatever you please.

Thanks for the link to MarkCli's blog.

re: Technology Previews of Visual Studio "Whidbey"

Ferris Beuller — Mon, 23 Feb 2004 13:49:00 GMT

Restrictions on releases just ignores the developers who do not sub to MSDN. I lost count of the CDs I got for free trial copies of VS.NET at trade shows. Just because its a pre prelease doesnt make any difference. Look at IE, theyve done pre-releases also to the public.

Showing reg codes for people that have licenses is just stupid really. Hey guess what "We dont want any new licensees", thats all it says. What about education users, they dont sub to MSDN. I can name countless reasons why its bad. You are only driving people awway to SharpDevelop, Borland or other IDEs. Do you want that?

As for the issue of managing public feedback, sure I can understand that but thats a different issue.

Weekly or nightly, probably weekly is enough for external and daily for internal testing for obvious reasons.

You will also get more buckets in watson for UEs by having more users out there than restricting it.

I for one do not sub to MSDN yet im a developer. Guess you dont want my products to add value to the platform then.

The cost of frequent bits updates

Riding Herd — Mon, 23 Feb 2004 18:32:00 GMT

re: Technology Previews of Visual Studio "Whidbey"

Jay Bazuzi [MS] — Mon, 23 Feb 2004 17:43:00 GMT

Koji: Glad to hear you're excited, too. I don't know what the schedule is. When I have more information, I guess I'll blog about it.

re: Technology Previews of Visual Studio "Whidbey"

Chris Garty — Tue, 24 Feb 2004 20:17:00 GMT

This is going to be incredibly helpful to software developers who are planning on delivering Whidbey-based business software.

Thanks for the good news Jay!

Notes From First Longhorn Experience

K. Scott Allen's Blog — Wed, 03 Mar 2004 07:21:00 GMT

VSS Label Differencing (on Longhorn!)

Korby Parnell's WebLog — Wed, 03 Mar 2004 20:59:00 GMT

re: Technology Previews of Visual Studio "Whidbey"

Sean Chase MCSD.NET — Fri, 12 Mar 2004 03:03:00 GMT

RequestForEditAndContinueFeatureInCSharp++;

Whidbey = Visual Studio 2005

Dan Fernandez's Blog — Sat, 13 Mar 2004 13:37:00 GMT

Visual Studio 2005 =

Dan Fernandez's Blog — Sat, 13 Mar 2004 13:37:00 GMT

Tech Preview now available!

jaybaz_MS's WebLog — Sat, 27 Mar 2004 08:59:00 GMT

Riding Herd — Sat, 27 Mar 2004 21:19:00 GMT

re: Technology Previews of Visual Studio "Whidbey"

dianyingxiazai — Mon, 02 Aug 2004 06:23:00 GMT

[href=//www.dmoz.net.cn/ title="wangzhidaquang"]
[href=//www.86dmoz.com/ title="jingpingwangzhi"]
[href=//www.kamun.com/ title="mianfeidianying"]
[href=//www.kamun.com/ title="dianyingxiazai"]
[href=//www.kamun.com/ title="MP3 free download"]
[href=//www.pc530.net/ title="diannaoaihaozhe"]
[href=//www.5icc.com/ title="duangxingcaixingxiazha"]
[href=//www.dianyingxiazai.com/ title="dianyingxiazai"]
[href=//www.yinyuexiazai.com/ title="yinyuexiazai"]