OmegaMan's Musings

I am running into this issue with Visual Studio 2008 Team System SP1 database project. It will allow me to drag one script but not multiple. I am publishing this to my blog to investigate, so let me explain.

Scenario

I have a database project with an active connection to the database and a few scripts. My goal is to drag my scripts as shown below to the active instance (a SQL Server 2008 instance to be exact)

If I highlight one sql script and drag it to the instance and I get this message:

It works and the script executed after I select yes. Note the text on the dialog, it clearly talks about multiples queries/scripts. Plural!

Problem

The problem arises when I select multiple scripts and drag them. At that point I am not allowed to drop:

Does anyone reading provide insight? Thanks!

I  upgraded my development box to Windows 7 and ignored, whistled past the graveyard as it were, the warning that SQL Server 2008 should be uninstalled due to incompatibilities. Upon the new OS install/upgrade I ventured out and tried to bring up the management studio. Much to my chagrin it crapped out on me, ya chagrin thats it.

So with that darned internet so handy I researched came to the conclusion, from the advice of the internet millions that SP1 should be installed to get it to work on Windows 7. Here is what greeted me for my efforts once as I attemped install:

Maybe you are reading this in the future where there is a flying car in every drive way and hanging a television on a wall is really passé because the wall is a TV; but as of this writing .Net 4 is only in beta.

So here is the text (a little trick which one can do is that on most dialogs one can do CTRL-C and get the text copied to the clipboard) as received:

—————————
setup.exe – .NET Framework Initialization Error
—————————
To run this application, you first must install one of the following versions of the .NET Framework:

  v4.0.20506

Contact your application publisher for instructions about obtaining the appropriate version of the .NET Framework.

So I leave it up to you my small but loyal (?) readership what is going on? Here is what I know

1. Upgraded from Vista to Windows 7.
2. Visual Studio 2010 version is installed but doesn’t run. So there is a version of .Net 4 on my system…
   
3. It all worked before I upgraded. ;-)

Thoughts?

In loading Visual Studio 2010 beta 1, I was very disappointed. Out of the box, the dialog menu text is fuzzy along with most dialogs. Here is V2010 and Visual Studio 2008 side by side. Notice the File menu text is fuzzy:

Notice toolbox is the biggest offender. Even the colors while editing are not as crisp. Is it just me or do my eyes fail when looking at VS2010? Someone has beat me to writing a Microsoft Connect issue on this one: Fuzzy text display in Visual Studio 2010 Beta 1.

string Fail = null;

for (int index = 0; index < 10; index++)

    if (string.IsNullOrEmpty(Fail))

    { 

        // Yes leave this empty

    } 

Yes it fails, and Microsoft, even though it was reported in 06, said they would fix it until what is now .Net 3.5.

People are up in arms on this issue….

But wait. There is a simple fix and the fix is not a fix because the code above is atypical in how someone actually programs and no real fix is required!

Here is how one can fix it:

string Fail = null;

for (int index = 0; index < 10; index++)

    if (string.IsNullOrEmpty(Fail))

        Console.Write(index);

In other words, don’t program empty constructs and you won’t have any problems! By simply doing work within the loop and not having an empty construct fixes the non problem.

People are up in arms that this should be fixed immediately! The nay-saying neighbobs of negativism are saying that a patch should be immediately done! Why hasn’t Microsoft fixed this. Some are suggesting that code out in the field at client sites are prone to failure and clients will be lost.

Oh, please…to reference a Forest Gump quote, “Programming is as Programming does”. If one is creating empty constructs and leaving it in code, that’s analogous to the person walking along the train tracks listening to music…who’s fault is it that they did not hear the train….hmmmm?

I had a request from a reader of the blog saying that he saw this summary on the RSS feed

And would prefer that to read the whole post and not have to deal with the … summary. Upon researching this issue, I have to surmise it is the RSS reader that is the culprit! The above picture is the RSS feed in Firefox, which I primarily use, and it displays the summary as shown above.

 But if I look at the RSS feed in IE 7 this is what I see:

To avoid this picture being cutoff by my blog style template, the IE has a right side widget that is a nice floating index along the which looks like this:

Summary

I guess the answer is that it is dependant on your browser or RSS reader….

In .Net 2/3 one can consume the NOAA web service WSDL at (http://www.weather.gov/forecasts/xml/DWMLgen/wsdl/ndfdXML.wsdl) and run into this error

  To get around this issue open up the generated reference.cs file and add this to the web service proxy class and rebuild and run

protected override WebRequest GetWebRequest(Uri uri)

{

    HttpWebRequest request = (HttpWebRequest)base.GetWebRequest(uri);

    request.ProtocolVersion = HttpVersion.Version10;

    return request;

}

Thanks goes to Rob Garret’s blog on this.

Here is my code snippet in C#

// Line 1
a++;
// Line 3

When I look at the output html the above snippet looks like this

<div>
   <pre style="padding-right: 0px;
               padding-left: 0px;
               font-size: 8pt;
               padding-bottom: 0px;
               margin: 0em; overflow: visible;
               width: 100%; color: black;
               border-top-style: none;
               line-height: 12pt;
               padding-top: 0px;
               font-family: consolas, 'Courier New', courier, monospace;
               border-right-style: none;
               border-left-style: none;
               background-color: #f4f4f4; border-bottom-style: none"><span style="color: #008000">

// Line 1</span>
a++;
// Line 3</pre></div>

If you look at thefont-famly it comes out as consolas and not console.

Update 4/2007: Clearing the Cache fixes this problem

We have been waiting for the new version but Firefox can’t handle the editor there is not edit area to edit in…