Skip to main content

MSDN Event: Visual Studio 2008 - Easton

Today I'm attending the MSDN Visual Studio 2008 launch event at the AMC Theatres at Easton Town Center in Columbus, OH. William Steele, Microsoft Developer Evangelist is fielding the discussion for the entire day: Visual Studio 2008, Astoria and Silverlight in the morning and IIS7/ASP.Net in the afternoon.

I've never seen William speak but I receive his updates via MSDN emails. He's handling the crowd well and is smooth with the slides and demo. After delivering a bunch of presentations and seeing others present, I just have the greatest respect for folks who can not only pull off a big event like this but do it with comfort and a bit of humor.

Topics included:

  • Visual Studio 2008 - what's new
  • .Net 3.0/3.5: C# 3.0/VB.Net 9.0, LINQ, anonymous types, etc.
  • LINQ
  • WCF/WF/WPF
  • ADO.Net Entity Framework - abstract/extrapolate physical data model into conceptual model (Beta 3 released 12/5/2007...RTM expected Q2 2008)
  • Codename Astoria - expose entities via RESTful web services (Official Name: ASP.Net Data Services)
  • IIS7
  • ASP.Net 3.5

As I've written before, I'm still in the "live events aren't the best use of time" camp but Microsoft does a great job of extending knowledge to the community in a free, all-encompassing event such as this. Further, when there's so much that's new and different, I find this "breadth blast" format is optimal. When I get free time, I can then drill down on topics I need or want to explore further (ADO.Net Entity Framework!)

Comments

Post a Comment

Popular posts from this blog

Hero Write-up: Now this is Customer Service!

My best friend Scott is president/C-everything of a small northeastern Ohio manufacturing concern, KirkKey Interlock . I hadn't spoken with him for a while and wanted to see how Canton fared with the Blizzard of '08 (that's what they're calling it...not me). I say, "So what's new?" He replies that on Tuesday his primary server (which essentially runs the business) came up with lame with not one, but [a statistically improbable] *two* physical disk failures on a RAID5 hardware array. My friend attempts the fix but gives up pretty quickly after seeing some Linux nasty-grams on the boot screen. His service provider is an old college buddy who lives down in Raleigh, Cerient Technologies led by Jason Tower . Scott couldn't email out because Exchange was on the toasted server. Being creative, Scott started Treo-emailing photos of the screen. Unfortunately, Jason couldn't receive email because a storm had knocked out a lot of local hosting. [Sigh] After...
4 comments
Read more

Certified or Certifiable?

As a senior technology professional, I interview a lot of candidates. I also maintain solid relationships with other folks in the community. Frequently, the topic of certifications arises: A good investment? Valuable? A clear measurement of skill? Consensus appears to draw the line related to one's seniority. If you're (for example) just out of school and looking for an instant creditability boost, by all means pursue a certification. Likely, this credential will assist you in overcoming the "junior" tag and likely land you more interviews and client roles. (Note: I'm going to use the terms senior and junior here...no offense to either. Can't think of a better one word description. I was a junior once too.) In stark contrast, the value of certifications drops off the table around the 2-3 year mark. Some in my circles even perceive certifications as a negative for the senior professional. They think, "If this guy is so solid, why is he wasting valuable...
5 comments
Read more

Lab Management in Visual Studio 2010 Released

In my experience, there's a lot of animosity and poor communication between Development and QA . It's not that they don't appreciate one another so much as they never seem to stay on the same page. QA : "What's the status on defect #4874?" Dev: "Done." QA : "Done?" Dev: "Yeah, I fixed that Tuesday." QA : "Err, ok . Well where is it? I mean where can I verify it?" Dev: "No clue. I committed it Tuesday. It passed unit tests and built successfully." QA : "Alright. I'll track it down." Invariably , QA speaks with the build manager (if there is one) to find the build in which that defect was repaired. After discovering the correct build, now QA needs an environment stood up to house that build. But wait, the UAT environment is currently testing the next release. It can't be disturbed for another week. At this point, the QA person's blood pressure heads for unsafe levels and the Dice.com bro...
1 comment
Read more