November 26, 2007 1:24 PM
Posted by: Brian Eastwood
VS 2008 and .NET 3.5
Can’t wait to dive into the hot-off-the-presses Visual Studio 2008 RTM?
Well, before you can do that, you have to install VS 2008 RTM. And before you can do that, you have to uninstall VS 2008 Beta 2 and its various and sundry components, libraries, runtimes and toolsets.
Scott Guthrie, the general manager of the .NET Developer Platform, provides a “complete list of potential Beta 2 components to uninstall” in an appropriately titled blog entry, Steps to Uninstall VS 2008 Beta 2 before installing the VS 2008 Final Release.
Meanwhile, Paul Glavich has written a bit about his Visual Studio 2008 Install Problems and Solutions. Glavich gets a gold star for embodying the mantra “If at first you don’t succeed, try, try again” — and for telling his story to the world on Thanksgiving.
Finally, as Guthrie points out, there is a Visual Studio Setup and Installation forum over on MSDN. A casual glance suggests that the forum has been busy in the last week or so. Raise your hand if you’re surprised.
UPDATED Nov. 27: More from Guthrie — Answers to a few VS 2008 Trial Edition, TFS 2008, and SourceSafe Questions, addressing in particular the way the new IDE interacts with Visual SourceSafe and Team Foundation Server.
UPDATED Nov. 29: The hits just keep on comin.’ Jon Galloway has upgraded three of of his machines from Visual Studio 2008 Beta 2 to the RTM release, and, like any good blogger, he has been keeping his eye on the issues that others have discovered. The end result of all this is a very helpful post called Ten Tips for a Happy Upgrade to Visual Studio 2008. Among the tips — be aware of some breaking changes to the ASP.NET ListView and to LINQ to SQL functionality.
November 24, 2007 6:56 PM
Posted by: Brian Eastwood
.NET Programming Languages
, Architecture and the SDLC
, Client applications
, Visual Studio and the .NET Framework
, Web applications
One of the commitments we made in changing our name from SearchVB.com to SearchWinDevelopment.com was to bring important information to our readers faster.
As we stated in our recent note to our readers, this blog represents that commitment.
The .NET Developments blog will bring you what you need to know about, well, .NET development, both on the front end and on the back end — not to mention architecture, testing, security and anything else that pertains to the process of creating .NET applications.
Here’s a tidy summary of what we intend to feature in this blog:
Breaking news. Admittedly, we’re not going to reinvent the wheel here — if we write an important story on SearchWinDevelopment.com, we’re not going to repost the whole thing here. What we will do is tell you why it matters and give you a chance to let your voice be heard.
Helpful resources. There are a lot of terms for these — tips, tutorials, how-to’s, learning guides and so on. We can’t even keep ‘em all straight. But we do know a good resource when we see one. We produce some of them (insert gratuitous plug for our Visual Studio 2008 Learning Guide here) and find a lot more in our travels around the Web. If we discover something useful, or manage to assemble one ourselves, we’ll let you know.
Software. There may not be such a thing as a free lunch, but there is free software. Plenty of it. Whenever Microsoft releases an important CTP or an SDK or a beta refresh, or whenever a interesting shared- or open-source toolkit emerges, we’ll link to it — and, since we’re journalists, not IT professionals, we’ll rely on you to let us know how it works.
Pertinent commentary. There are a lot of people out there who are a lot smarter than we are. Many of them are probably reading this right now. When they say something meaningful about the world of .NET, we’ll pass it along.
There’s one theme throughout those four features, .NET development and architecture notwithstanding — we want you the reader to be involved.
As we all learned in the early days of school, likely between snack time and nap time, we all benefit from sharing. If you have a tutorial, a software download, an opinion, a correction, or a prediction, by all means share it with us. And if you think you might want to be a regular contributor, let us know. Our category list shows that we intend to cover a lot of ground, and, well, we can’t do it alone.
So that’s our story, and we’re sticking to it. We’re glad you have decided to join us on this ride through the blogosphere, and we look forward to hearing from you.