Ideas I think the SQL Server team could use to build some future products. These most have to do with SQL Server Management Studio tools improvements that would be leveraged (in time) into Visual Studio.
Recently in Visual Basic 6.0 Category
Despite the fact that you’ve used the encryption option on your SQL Compact database, if you don’t hide the password, it’s really easy to figure it out. I suggest you (at least) use an obfuscator or better yet, your own (private) technique to hide the value. Consider that there are ways to “reflect” the underlying source of .NET programs because they are stored as CLR intermediate language on your client’s system.
Patrick, I could not agree more with your editorial this month. Based on what I hear when I leave my cave is that Microsoft just doesn’t get it. Because of politics (no, not the Bush/Obama kind) and an old-school marketing and sales plan, Microsoft has also forced its own development teams to pump out new versions of SQL Server and other serious platform engines on a ever-shortening cycle. The same is true for Visual Studio and the languages teams whose development cycles seem to be totally consumed trying to get the Entity Framework working. This means the teams place less emphasis on fixing existing long-term bugs and making development of existing architectures easier. Over and over again we hear that “Microsoft knows what’s best for developers”.
Having seen the litany of non-answers (and random guesses) on the SqlClient.SQLException:
"A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)"
I decided to figure this out for myself. No, it has nothing to do with named pipes or TCP/IP protocols or using wireless connections or VPNs--it has to do with the SQL Server instance configuration. And no, you don't have to disable connection pooling. Frankly, I would be surprised if lack of a connection pool would fix the problem.
I'm giving my ever-popular Pragmatic Application Design workshop that's been newly updated to discuss the latest SQL Server 2008 and Visual Studio 2008 SP1 upgrades. And yes, DevTeach is including a copy of my book "Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)" to everyone signs up. It's a $59.99 value! Well, it's really $37.79 at Amazon, but it's still worth it.
DevTeach and SQLTeach are announcing a rebate for 350$ with your TechDay coupon...
What? A rebate of 350$? How is that possible! Well if you still have your TechDay/DevTeach rebate coupon you can use it for the December Montreal event and you will get a 350$ rebate. Originally the coupon was good for 100$ rebate but we like Microsoft so much that DevTeach changed its database and the coupon you have in your hand is worth 350$! This rebate will be effective until December 2nd. So hurry, don't miss the opportunity to attend a conference with renowned speakers coming from all over the world.
And there’s even more. Just announced …
Every attendees will get Visual Studio 2008 Pro, Expression Web 2 and Tech-Ed DEV set in their bag!
DevTeach believe that all developers need the right tool to be productive. This is what we will give you, free software, when you register to DevTeach or SQLTeach. Yes that right! We’re pleased to announce that we’re giving over a 1000$ of software when you register to DevTeach. You will find in your conference bag a version of Visual Studio 2008 Professional, ExpressionTM Web 2 and the Tech-Ed Conference DVD Set. Is this a good deal or what? DevTeach and SQLTeach are really the training you can’t get any other way.
And yes, I'm not the only speaker. There are a bevy of French and English speakers to bring you up to speed on the latest Microsoft technology.
I had another question in the newsgroups about converting existing VB6 applications to VB.NET. We had already discussed the fact that ADO and ADO.NET are about as similar as bicycles and motorcycles. The thread progressed to the question of creating a non-targeted application that would work against a variety of back-end databases like SQL Server, MySQL and FoxPro.
Here's my answer...
One of the "inside" aliases that I monitor posed the question: What should a (very) introductory Visual Basic .NET course (for college students) contain? At least one response went into some detail that (IMHO) missed what students getting started as programmers really need to know.
I might start (a very introductory course) in much the same way as I did when I taught CS101 to college students. Let’s assume, that these students know these foundational concepts—what’s a CPU, what’s RAM, disk, and the rest. Can we assume that these students are going to need know how to solve business problems with a computer program they have written themselves—as opposed to doing it with ledgers, 3x5 cards or Excel?
To do so they will need to know how to:
• Learn what needs to be done. This might mean interviewing customers those that will use the application and understanding the problem they are trying to solve. Too many developers come up with a solution to problems that don’t exist or don’t address the customer’s problems.
• Learn how to design before coding.