Public musings, often on software development RSS 2.0
# Friday, January 04, 2008

So it's a new year... and time to get working on getting back on my bike again.  I managed some riding this past year which was good - but not nearly as much as I'd hoped.  I've fallen about 2,400 miles off my target annual mileage... oh well, hopefully I'll hit or exceed my target this year - although in all honesty I think it'll be difficult to hit my target again this year.

On the plus side my light is working again, I was unable to ride to and from work for most of Dec. because when I pulled out my light it stopped working.  I have a very nice Flamethrower from NiteRider (www.niterider.com).  (The flamethrower was the 1st generation the current generation is the Flight: http://www.niterider.com/prod_flight.shtml) This light puts out more light then most car headlights - which is good because when I'm riding at night I want to be seen and this isn't a headlight that you can miss.  Unfortunately on my first ride home this winter; when I fired it up - the LEDs powered up but each time I tried to get my main light to start it failed.  I made it home, after all the 3 LED's do provide minimal light - but not an acceptable situation.

So I used the NiteRider website and gave them a call.  Their service was well coordinated and they gave me a Return Maintenance Authorization (RMA) number to track my repair.  So I sent them my light, at the height of the Christmas season...  A couple days after FedEx showed my package had been delivered I gave them a call to check on the status.  Note I didn't send them my battery because they charge $20 for each returned item (light, battery) and since my LED's worked, my taillight worked and my light was trying to fire up I felt the battery was solid.  When I spoke to the maintenance rep he mentioned he was preparing to call me... the problem was a bad ballast and the light had been given some free maintenance beyond the ballast.  So I paid for the light's bench test and parts.

I got it back a few days later and set up a test at home (no sense repeating my last ride).  Well I fired up the light - and same results.  Now I have no doubt that they tested my light before shipping it back to me so I called them back.  Of note I didn't start screaming or looking to kill the phone guy, I just said hey - got my light but it still doesn't work.  We talked a few minutes and we agreed I would send my light and battery back and they would waive the bench fee on the battery as long as it checked out (we all knew it would) and (still in the Christmas season) they put a rush on the work order.

A few days later I got my light and battery back - no charges, apparently something else related to the starter in the light or the light itself had failed (probably took a hit in shipping) and they had repaired my light and gotten it back to me in a matter of days.  Overall although it did take two trips (for the FedEx guy) they did a great job getting my light back online (although I was on vacation by then). 

Today I hooked up the light and rode into work - yes I had tested it previously. The goal is to get to ride in 3 days a week, and I'd ride tomorrow but it looks like the rain really will arrive tomorrow so I'll wait till next week to ride in again, but my thanks to the folks at NiteRider who did a great job with my light's repair and now I just need to get in a couple thousand miles...

Friday, January 04, 2008 12:14:09 AM (Pacific Standard Time, UTC-08:00)  #    Comments [0] -
Cycling
# Sunday, December 23, 2007

Sunday, December 23, 2007 10:36:36 PM (Pacific Standard Time, UTC-08:00)  #    Comments [0] -
.NET | Visual Basic
# Thursday, December 20, 2007

Many years ago there was a common pattern for Office Workers.  Essentially before the true abundance of desktop systems and printers it was common to have a paper form.  Copies of this form would be used for any number of tasks (fax cover sheets are a common example most people can relate to) and then when there weren't any copies left you would make a new set of copies.  The cardinal sin for the admin staff was of course the person who took the original and used it instead of copying it.  Want to really get on the Admin staff's bad side wipe out 3 or 4 originals and they will hunt you down...

At any rate now that we have PC's and easy access to printers the separate set of file folders containing originals hidden from non-admin eyes is pretty much a thing of the past.  These documents are typically stored on a central Intranet server like SharePoint.  However, in many cases a limited version of the same problem still exists.  Now people will take the copy that is on the server and open it for customization.  Then without thinking they save that copy and it goes right back to the server.  In minor cases they've just poluted the baseline copy that's sitting on the server - but in extreme cases they could so modify the original that its almost useless as the original.  The solution of course is to make such original copies read only, except now instead of having them under lock and key in a big old file cabinet - they sit online marked read-only or checked out to the one trusted individual who won't overright them...  It's the same solution to the problem, just implemented with 21st century technology instead of physical copies.

------------------------------------------------------

Sorry for the long delay and somewhat sparse posts over the last few weeks (OK Months) but I've been a little busy with the latest version of the Professional Visual Basic book to go along with Visual Studio 2008 and VB 9.  However, I reached a milestone last night - OK theoretically it was early this morning.  I caught up with my publisher.  I've turned in all my draft chapters and returned all of the edited chapters that were returned to me to date.  I'm not yet done because there are more edits that need to be returned to me - of course the fact I turned in the draft late might be impacting that... but for tonight at least I don't have any authoring commitments... except I'm supposed to start that magazine article...

Thursday, December 20, 2007 4:12:50 PM (Pacific Standard Time, UTC-08:00)  #    Comments [0] -
Musings
# Friday, November 30, 2007

So one of my biggest pet peeves with the release of VS2008 was the fact that if I created a WPF project in VS 2008 or even converted it to work in VS2008 - then I was stuck - no more taking that project into Blend to work on the graphics.  This to me was a significant issue.  Fortunately Soma announced that this issue has been resolved and Blend SP1 which supports the VS 2008 project files is now available. Here are the links:
Soma: http://blogs.msdn.com/somasegar/archive/2007/11/30/designers-and-developers-working-together.aspx

Blend SP1:  http://www.microsoft.com/downloads/details.aspx?FamilyID=a07196d1-971b-4710-99c8-d3d9603ccfcb&DisplayLang=en

Friday, November 30, 2007 12:31:47 PM (Pacific Standard Time, UTC-08:00)  #    Comments [0] -
.NET | Technology
# Friday, November 23, 2007

Once I installed Visual Studio 2008 it was time to add the Team Explorer for Visual Studio 2008.  The Team Explorer aka Team Foundation Client is found on the Team Foundation Server installation DVD.

So I took the .ISO file which I downloaded from MSDN and copied the TFC folder which contains the Team Explorer installation onto an actual DVD.  This gave me a copy of just the Team Foundation Client 2008 which I could install onto my development machines.

I put the DVD into my Vista/Office 2007 machine and kicked off the install.  The install ran and after things were going I moved onto another machine.  When next I checked I found that the installation had failed.  So I reported the failure via the automated process that the install package provided and tried again.  The install failed again - which left me... concerned.

So I took the DVD out of my Vista machine and moved to my Windows XP / Office 2003 machine and ran the installation.  While that was running I started searching the web for any known installation errors with Team Explorer 2008.  I finally found a note in the Microsoft MSDN Forums that mentioned someone else was having an install problem and found that it went away when they used the install from a DVD which had all of the TFS products, as opposed to a CD with only the TFC folder.

Now what was interesting is I found this as my Team Explorer install on Windows XP with Office 2003 completed successfully.  In other words on an XP machine running Office 2003 you only need the TFC directory to install Team Explorer.

So I went to my .ISO file and burned a DVD of the entire image this time and put it into the Vista/Office 2007 machine.  I must admit I really like the updated install package for the TFS product, having the different product options available is a nice way of handling the different install packages.  At any rate I clicked on the Team Foundation Client and started the install.  The first and subsequent screens to start the installation looked just like the stand-alone DVD's and the install started with the same packages.  However, in this case the installation ran to completion.

Thus if you are using Windows XP with Office 2003 you can install a standalone installation package for Team Explorer however, if you are running Vista or Office 2007 and you get an installation error - then make sure you get a copy of the full Team Foundation Server (TFS) DVD and run the install from that media.

Friday, November 23, 2007 1:01:54 PM (Pacific Standard Time, UTC-08:00)  #    Comments [0] -
.NET | Team System
# Tuesday, November 20, 2007

So for those who weren't aware Visual Studio 2008 released on Monday November 19th.  I got my download started early while the downstream transmission speeds were still above 300KB and it finished late yesterday afternoon, early evening when the transmission speeds were down under 70KB.

So like many who have been using Visual Studio 2008 Beta 2, I made the decision to install Beta 2 on my main desktop (physical machine).  This was a good decision as I've been using Beta 2 for projects for the past 4 months.  However, now it was time to face the music - would I need to rebuild my box to get the release version installed?

As part of working on the next Version of Professional Visual Basic for Wrox, I have a virtual environment which was configured for my authoring and screen shots.  So it became my test platform.  I started the uninstall of VIsual Studio 2008 Beta 2, I uninstalled MSDN, and as I looked at the list of other products some of which hadn't uninstalled I found several that were from 7/27 the day I installed VS 2008 B2 and I could tell they were related, so I uninstalled them as well.  I then took a couple minutes to rename my old projects directory to "B2" since I plan to rebuild the projects from scratch and I made sure other directories that VS would target were also clean. 

So I took a fairly conservative approach to minimize the risk that it would fail.  I rebooted and connected my VPC to the ISO which I downloaded and kicked off the install with crossed fingers.  The installed started no problem.  Nearing the end of .NET Framework version 3.5 was install my Vista machine asked me to reboot and restart my installation, which I did.  The installation then ran to completion and asked for another reboot.

I then installed MSDN locally and again everything went fine.  So for those wondering installing the release version of VS 2008 on a machine which previously ran VS 2008 Beta 2 seems to a non-issue.  So get out there and get the latest bits and start working there are a ton of new features to explore.

 

Tuesday, November 20, 2007 11:02:43 AM (Pacific Standard Time, UTC-08:00)  #    Comments [0] -
.NET | Technology
# Friday, November 16, 2007

It's Friday so in a slightly more light hearted spirit I thought I'd link to a less serious post.  I for one have written about and certainly talked about the persona Mort.  Mort for those not up to speed is a Microsoft 'persona'.  Microsoft created these persona's to help them focus on the type of person that used a given product.  Paul Vick has a fun little post describing (with pictures) three of the main developer persona's and suggesting that it's time for Mort to retire. http://www.panopticoncentral.net/archive/2007/11/14/22589.aspx 

My personal opinion is that Mort took a bath and learned C# a long time ago, he's got a big velvet Elvis hanging in his trailer.  (I'm saying this in the context of Paul's post) Thus from the standpoint of VB retiring Mort only makes sense, and I find the Ben persona much more appropriate :-)

Friday, November 16, 2007 2:11:24 PM (Pacific Standard Time, UTC-08:00)  #    Comments [0] -
Visual Basic
# Thursday, November 01, 2007

This winter I'll be taking my first crack at a new class at the UCSD Extension.  It's surprising that I'm heading into my third year teaching the Visual Basic .NET Programming II class and now I'll get to do my own lead in.  I'm looking forward to this opportunity especially since I'll be updating the materials to account for Visual Studio 2008.  As always I'll make certain the course supports those who only have access to the VB Express Edition in terms of lab work.

So if you are looking to learn about the most powerful and most popular .NET language, stop in for a class.

For more information on the when and where and if you are interested in registering for the course go to the UCSD website at: http://www.extension.ucsd.edu/studyarea/index.cfm?vAction=singleCourse&vCourse=CSE-40615&vStudyAreaId=14 

Thursday, November 01, 2007 9:44:06 PM (Pacific Standard Time, UTC-08:00)  #    Comments [0] -
.NET | Technology | Visual Basic

Often as a new release of Visual Studio approaches there are posts regarding, where are the two primary languages in .NET going?  In short as has been noted on one or two places around the net the VB MVPs posed the question of, what is the strategic long term expectation for VB and how is VB doing in the market?  Which language should I learn, which will help me get a job? etc.  

(The short answer regarding which language to learn is - if you are going to do just a little programming VB is easier to learn and maintain.  If you intend to be a Professional Software Engineer and limiting your career to being a full time Cubicle Code Monkey you need to know both. Just knowing C# or VB isn’t enough, as a developer I’ve learned somewhere between one and two dozen programming languages, to be honest I lost track of them all and stopped counting long ago – although interestingly enough I still have my high school ‘Basic’ programming book...sentimental value only - the point being casual developers will be more comfortable in VB and professional developers learn languages and VB and C# are both necessary with .NET today.)

 

At any rate focusing on the core topic, depending upon where you ‘stand’ your view of VB or C# might be that it’s doing great or not so great.  After all if you are working in a shop where your senior management likes C# it might seem like very few people are working with VB. 

 

On the other hand this perception might be a self-fulfilling prophecy for your company. After all if every project uses a hammer then there must be a lot of nails (how’s that for twisting a proverb “if all you have is a hammer everything looks like a nail”)  If your company “supports” both VB and C# languages but encourages that new projects use one language well then you begin to wonder.  As I noted in the past I’d consider that pretty short-sighted for a consulting company.  After all if your goal is to sell software as a service (which consulting companies do) you don’t want to lose a major portion of your market to language bias… so before I go further I want to clarify where I got some of the data I’m about to toss out.

 

I think it’s common knowledge that I’m an MVP (I can hear some of you: ‘could he mention it one more time…’) anyway I bring this up to note that it shouldn’t be a shock to realize that as an MVP I have a Non-Disclosure Agreement (NDA) with Microsoft.  This comes up because as a group we MVP’s have some communication channels (formal and informal) with Microsoft.  One of the formal ones revolves around my specialty area Visual Basic.

 

In this area the VB-MVPs have essentially an opportunity to truly speak freely to Microsoft on NDA topics.  It’s where we can say we think that feature A is useless or that we think the VB team has dropped the ball by not having a given feature, or where we think they need to take the ball and really run with it.  It also allows us to ask questions and get answers that might embarrass one or more people at Microsoft.  In general it is a valuable tool.  Every so often we get permission to post some information from that discussion to help frame discussions outside that group – things that aren’t too germane to actual company business, and that’s the case for the numbers I’m about to post.

 

There are way more people online downloading C# right?  Wrong – At this point you aren’t going to be surprised when I say the VB Express is the top download of the Express editions.  It probably also doesn’t surprise you if I say that it’s downloaded far more frequently then C++ Express.  But does it surprise you when I note that C++ is the number 2 download behind Visual Basic.  It surprised me, after all I expected Visual Web Developer to be in the top 2 (after all both VB and C# web developers would use that one tool).

 

That’s right Visual Basic alone is more popular by a margin of 20% over C++ <credit VB Team>.  What I will say is that the other three express editions are all much closer in terms of downloads, and registrations.  The point is that Visual Basic is noticeably more popular. Of course this is the Express Edition, that’s for students and hobbyists, they aren’t professional developers.

 

So how big is Visual Basic when someone reviews the market?

Well according to Forrester research Visual Basic is the #1 .NET language. <credit VB team>  Note that’s not some legacy number based on COM developers, that’s just in terms of .NET developers.  That’s right the majority of professional developers out there are using Visual Basic, and that even makes sense.

 

Think about it this way, prior to .NET the two primary development languages were C++ and VB.  C++ was far more powerful, but it took longer and cost more to develop applications.  Sure for someone developing tools or with a huge install base the disadvantages could be overcome for the power.  VB on the other hand was much easier to learn and use, the code was easier to maintain and its performance while not equal to, was certainly comparable to C++.

 

Along comes C#, from the standpoint of C++ developers C# offers a familiar syntax and reduces the disadvantages of C++ - applications were easier to develop and accordingly cost less.  C++ developers and Java developers have without a doubt flocked to C#.  In fact if you are a Java developer and haven’t moved to C# boy are you missing out on the future.  However, these were smaller developer communities to start with then Visual Basic which also released a .NET version.

 

Visual Basic also moved to .NET and its disadvantage – not having the same runtime environment and power as the other major language went away.  Note the fact that VB is easier to learn, read and maintain is still true but now you also get all the power of C# and since .NET creates code on par with C++ it means you as a VB developer are creating first class applications.

 

Sure some people have jumped from VB to C# that is to be expected, and many companies which in the past would have C++ for some projects and VB for others are moving to use only 1 .NET language.  However, as I’ve noted in the past most VB developers will find the transition to VB.NET fairly easy and natural.  When I teach I find that the students with previous VB experience do very well, and in fact that once they get the key elements of Object Oriented Development are ready to become productive.  More importantly the VB teams recent move from a migration wizard to the Interop toolkit (similar to WPF Interop) and the Power Packs make the transition from VB6 much easier.

 

What is interesting is how the VB team blog (http://blogs.msdn.com/vbteam/) ranks in the top 1% of all MSDN blogs and the fact that the VB Developer center on MSDN is one of the top trafficked sections of MSDN (http://msdn2.microsoft.com/vb). <credit VB Team>  In other words VB is doing just fine and as I’m sure we would all agree so is C#.  In the near term there is no reason to suspect anything about this equation will change – C++ and Java developers will tend to prefer C# and those who have mastered both VB and C# will prefer VB J

 

So what about the future?

Well for starters the Visual Basic team recently published the Beta version of the Visual Basic language specification.  A great step for defining how the language works, and one I look forward to seeing become the basis for standardization.  We also know Paul Vick is discussing VB X (aka VB 10)  over at Panopticon Central (http://www.panopticoncentral.net/) and is very open to input on things to deprecate in the languages specification and new language features to add.  I highly suggest going over to get in a good suggestion or two.  As for Visual Basic – I’m confident that it’ll be around and diving into all corners of the Microsoft development tools.

Thursday, November 01, 2007 1:06:18 AM (Pacific Standard Time, UTC-08:00)  #    Comments [0] -
.NET | Musings | Visual Basic
# Tuesday, October 30, 2007

So this is a quick post to place my vote on the recent changes to daylight savings time.  When it comes to movng it earlier in spring back toward Febuary, that works for me. 

However, moving it from the last Saturday in October to the first Saturday in November messes with Halloween.  Instead of it getting dark an hour earlier so that the Trick or Treaters get out earlier and finish earlier - everyone waits for dark to fall and the result is: Trick or Treaters are out for almost an hour later at night.

I know that some will say that having the sun out makes trick or treating safer but as was shown tonight - that is only true if people change the habit of waiting till dark.  We didn't base our trick or treating when I was growing up on a time, we based it on sunlight -when it was gone we got to go out.  So don't make up alot of claims about safety, the reality is this is one of the few nights (July 4th is another) when kids get to go out after dark.  And as I recall we kids love that aspect of it.  So instead of everyone being done by 7:30 or 8 they are finishing up around 9, meaning they are out later which is in my opinion a bigger risk. 

So with all due respect, to everyone's claims of non-existant energy savings and safety, put daylight savings time back to ending at the end of October, Thanks

Tuesday, October 30, 2007 11:07:51 PM (Pacific Standard Time, UTC-08:00)  #    Comments [0] -
Musings
Archive
<January 2008>
SunMonTueWedThuFriSat
303112345
6789101112
13141516171819
20212223242526
272829303112
3456789
About the author/Disclaimer

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

© Copyright 2012
Bill Sheldon
Sign In
All Content © 2012, Bill Sheldon