10/17/2007 5:10:55 AM

why is my 'create new database' function in my Visual Studio Express Editions( VB,C# and VWD) disabled

joseph

10/17/2007 5:10:58 AM

Some people forget that the How-Do-I Videos are for help, training and instructtional use.
We should never exclude one group from another.

John J Ross

10/17/2007 6:01:02 AM

Sorry no comment on your How-To videos... other than yeah, I would rather see C# than VB... but only because I have personally moved on from VB... about 6 years ago...

Side note:

I kept seeing JavaScript errors when I load you blog... so I dug under the covers to discover why.

The date countdown script you have is in need of some tuning:

====your code====
window.onload=function(){
fixDate();
}
<!--this is an interval of three hours that checks for a date change -->
var intervalID = setInterval(fixDate, 10800000);
var count=1;

function fixDate(){
var eventDate = new Date("February 27, 2008 07:00:00")
var today= new Date(Date());
<!--the difference in milliseconds -->
var myNum=eventDate.valueOf()-today.valueOf();
<!--converting to days -->
myNum=myNum/86400000;
<!--rounding the crazy numbers -->
var newNum=Math.round(myNum);
<!--put it in the table -->
myDate.innerHTML=newNum;
}
====your code====


====revised code====
window.onload = function(){
fixDate();
}
/*this is an interval of three hours that checks for a date change*/
var intervalID = setInterval(fixDate, 10800000);
var count = 1;

function fixDate(){
var eventDate = new Date("February 27, 2008 07:00:00");
var today = new Date();
/*the difference in milliseconds*/
var myNum = eventDate.getTime() - today.getTime();
/*converting to days*/
myNum = myNum/86400000;
/*rounding the crazy numbers*/
var newNum = Math.round(myNum);
/*put it in the table*/
var myDateElem = document.getElementById('myDate');
myDateElem.innerHTML = newNum;
}
====revised code====

The comment style was wrong, but that didn't cause the errors... the "myDate" direct reference did.

In IE's world of non-standards, it pollutes the global namespace with variables for each element with an ID. This causes all kinds of fun when you assign IDs like "document", "window", "frames", "location", "body" etc.

Using the ECMAScript standard DOM Method of document.getElementById( id ) is a much cleaner way to access the element in question.

I'm curious about the setTimeout though... are you expecting visitors to stare at a post here for over 3 hours, and expect the countdown to adjust? I suppose if you were to leave your PC on, and go to bed, maybe....

Oh, and I think the count variable is not needed anymore...

Steve

10/17/2007 6:02:12 AM

Joe,
I couldn't agree more, whoever reads c# reads VB and not so easilly the opposite. I have nothing against c#, quite the oposite, but one of the most important things about this site as a resource guide is its vast amount of explanatory videos, wich have been very concise.

the more the better !

Rui Silva

10/17/2007 6:15:56 AM

all examples should be in byte code!!!

bob

10/17/2007 6:21:40 AM

I totally understand with that stance. I think the people that may have the most problem with videos in VB are those that are just approaching the .NET platform, e.g. it's a logical transition for a C or C++ programmer to choose C# as the syntax is a derivative of the language they have knowledge of. Sometimes the hurdle can be to map the VB.NET language constructs to their C# counterparts, sometimes this requires a little research from the viewer as it's not obvious.

My personal opinion is that if you have a good understanding of imperative languages as a whole (although C# is my preferred language I've also taken the time to use several other imperative languages like Java (don't shoot!)) then the transition between imperative languages becomes very easy - syntax is generally very easy to learn if a language has well defined constructs which all major imperative languages do (VB.NET included).

If you were doing the videos in a functional language for example which is a paradigm shift then I thnk people would have more ammunition for such videos.

Granville Barnett

10/17/2007 7:13:54 AM

I'd like to take this oppertunity to thank you for the tutorials you've posted, I'm looking for a new ones every day.
Thanks

Kristian

10/17/2007 7:47:41 AM

No problem Joe, i'am a C# programmer but the videos are useful independent of the programming language.

Jorge Salinas

10/17/2007 8:16:16 AM

I think you're excluding the non VB and C# coders. What about VB6?

Only kidding -- I think VB is fine. If I program in C#, I shoudln't have any trouble understanding a VB application.

Dave

10/17/2007 9:16:33 AM

I agree with Jorge, I have never programmed in VB but the videos are really easy to follow, and VERY helpful.

Anderson Fortaleza

10/17/2007 9:58:58 AM

VB Rocks!!! Keep doing them in VB, you will get things done (CTL+B) much faster than (CTRL+B) C#. Plus you (CTRL+B) you will know (CTRL+B) if you actually (CTRL+B) have any syntax (CTRL+B) errors quicker, than (CTRL+B) C#. Man I wish (CTRL+B) I had not written (CTRL+B) this comment in (CTRL+B) C#.....

Chris Love

10/17/2007 11:04:18 AM

Got post bro...It makes perfect sense.

btw, I'm the one who ran the VB support BBS for MS wayyyyy back in the day.

Mark Wisecarver

10/17/2007 11:04:34 AM

Thank you for the great How-Do-I videos, if it wasn't from the, I would still be programming in asp classic!

Seid K.

10/17/2007 12:05:21 PM

The question is support? Is MS supporting C#? By not doing something in c# but doing it in vb.net sends a sublime message that vb.net has more support. Now that is not to say that I can go and find a boat load more of c# than vb.net, so the question is equality. Do what you do for one for all the other(s). Is MS eating their own dog food? Is MS lacking resources that they can't make both? Have as many whatevers(videos, samples, write ups) for all and not cut down on quality nor quantity. No money, no time, no resources? Or is it that C# programmers are smart enough to figure it out that MS figures we don’t need help, support or videos? Now that I see F# coming along into VS2008 is that going to be fully supported half-way, or less than c #? If MS doesn't use it why should I. By choosing c# now, is MS 5 years from now, because of more VB programmers stop the support for c# all together? Is this a trend or a mistake? Supprt them all and support them equally. If you do something for one repeat for all the other(s).
If you need some help I can send you my resume?

guy

10/17/2007 2:19:20 PM

I will CONTINUE to program in VB to ANNOY my C# friends. C# is over hyped!
I am YET to see what you can do in C# that I cannot do in VB, yet C# programmers are the loudest complainers.
keep up the good work,
yousaid

yousaid

10/17/2007 4:16:22 PM

Whether it is C# or VB, is matter of personal preference. It's up to the reader to catch up or understand the syntax. But the tutorial video should support both languages because i believe MS can afford the resources to make it happen. Just a thought.

Keep up the good work..You're helping a lot of developers in the community.

Willie

10/17/2007 6:10:38 PM

I think there are a lot of people who would like to see videos in C#, but I think it makes a lot of sense (for reason you already pointed out in your blog) to do the videos in ASP.NET. The videos are nice because the programmer will often clue the viewer into the issues they have run into and tricks they use to be more efficient. I think it would be nice if 2 forum links (1 for ASP.NET/ 1 for C#) were added to each video so asp.net community members could discuss the videos, tips, issues, etc. Just a suggestion, not sure how many people would use it though.

Don

10/17/2007 9:12:52 PM

They are so easily interchangeable that's it's a silly thing to be religious about. C# is more more elegant to write, but the point of source code is to communicate with other humans, and VB is more human readable-- it's practically self commenting. And since communication is the point of the videos it's the natural choice (if you have to make the choice).

Wes

10/18/2007 2:39:12 AM

I am a LSD for a small dev team... 2 VB'ers and 2C#'ers. We often compare languages and so far we found the following:

1. VB is ALOT quicker to get an app out the door
2. VB is more verbose, but the IDE does all the 'filling in' for you, so less time spent pecking at the keyboard (the C#'ers are envious about this!)
3. VB compiler pre-warns you of compiler errors before you even (Ctl-B)!
4. There is no speed difference between the 2 languages for the same compiled app
5. There is only 1 functionality we use that VB can't do but C# can
6. There is about 4 functionality that VB can do that C# can't
7. We now have one of our C# developers converted to VB - and he loves it!

Our conclusion is that both languages are equally powerful, but VB is more productive. VB is easier to read and understand than C# so language migration is easier from C# to VB, but not too difficult from VB to C#.

In a nutshell, VB rocks! and the videos prove it! Keep them up, we love 'em!

CDSofty

10/18/2007 5:29:40 AM

Well, I agree for the most part, that vb is easier to grasp for the masses and then c# developers can then determine the key differences in the language. They are also able to download the C# specific code also.

I also think that Microsoft is also looking to help move all of us old asp classic and vb6 programmers off of the old code, so this is a great way for them to accomplish this. If it wasn't for the video's, I'd probably still wouldn't be considering moving my code to .net. I have limited amount of time to learn .net code (since I'm not a full time programmer) so the video's are great for me to learn something quickly, and visualy and to see it in action to be able to upgrade parts of my website and/or vb 6 applications.

Keep up the good work with the video's, either direction, they are fantastic.

Terry

10/18/2007 7:01:03 AM

I don't mind whether these are doing in VB.NET or C#, providing it doesn't mean MS is planning to ditch C# in favour of VB.NET. Along with the recent announcement of increased PHP support, some of us may start to worry about the ASP.NET / C# route.

BG

BG

10/18/2007 9:45:33 AM

I've got the global answer to that question: Becuase VB pwns C#'s wimpy ass!

Keep up the fantastic work on the videos, and stick with VB. They are perfect! These videos are just another thing that elevates ASP.NET above all other wanna-be web development languages.

Josh Stodola

10/18/2007 3:45:01 PM

can u tell me how would i use an embed code and put it on vb

bloodyr

10/19/2007 10:16:21 AM

You should learn how to spell before writing for publication.

Larry

10/19/2007 11:19:33 AM

"The question is support? Is MS supporting C#? By not doing something in c# but doing it in vb.net sends a sublime message that vb.net has more support. "

I think this door swings both ways though you may not see it unless you're sitting in the shoes of the given developer. An illustration of this is that when VS add-ons come out they typically only support C# at first (e.g., where the Sharepoint extensions came out, they were only in C#). I could switch to C# but I have such a time investment in VB that I'm going to stick with it until I have a compelling reason to change. I have not run into a task that I couldn't do, and do well in VB. Plus, being that they're all run under the CLR if there is an instance where it saves you time to use C# (say, you find a Framework already written in it) then compile it and add the assembly to your VB application. A purist would scoff and translate the Framework's source, a realist would save that time and move onto the next task since the end user doesn't care either way.

Either way, I love that the .Net framework gives you the ability to choose your language of choice. That ease of use and of choice is one of the main reasons I've stayed a Microsoft fan in the face of IMO a much more time consuming and tedious development process in Java.

John

10/20/2007 1:38:48 PM

I'm a self taught VB programmer who can't read C# hardly at all. So I really appreciate your decision to use VB. Otherwise, I couldn't really follow the videos.

As a VB programmer, I'll admit that many VB people just aren't as experienced as the average C# programmer. A lot of the reason for the VB language was created was to teach newbies how to program (though the language has grown up since then). So, when doing a video that aims to teach people how to program, it makes sense to use VB.

tim

11/1/2007 7:24:57 AM

Total BS. VB run some of the apps in the financial centers, inclusing the big street! Why? Because it's RAD, no time to waste, easily read and all devs on a team can understand. Time is money people. That's one of the things a real developer should learn.

sk