Monday, September 29, 2008
High Contrast
It really is a bummer that Windows and Mac can't accommodate a dark, (or high contrast) color scheme. I'm trying it right now. It is much easier on the eyes, but lots of images and applications are wonky.
Wednesday, September 24, 2008
Tuesday, September 23, 2008
SQL Server Management Studio Colors and Themes
I have become quite fond of darker color themes in Visual Studio. Once you get used to it, it is a bit harsh to go back to the white background of SSMS. It is sort of a bummer that the "Import and Export Settings" tool that is available in VS is not available in SSMS. There is a settings file at C:\Users\(me)\Documents\SQL Server Management Studio\Settings\CurrentSettings-(date).vssettings, but I didn't want to waste time dorking around with it. I just found a tool here that imports your settings from VS into SSMS. I downloaded the source, but the project didn't work for me, but since it is really just a one file console app, I made a new project for it. It is super fast and looks great.
Friday, September 19, 2008
A Good Feeling
Me (to self): Um ... how does this work? ... Oh yeah, I'll go look at my unit tests."
Background: I have slept since I built my services and tests. I have forgotten everything. But happily, the unit tests told me everything I needed to know, and I have now spent more time on this post than on the actual problem
Background: I have slept since I built my services and tests. I have forgotten everything. But happily, the unit tests told me everything I needed to know, and I have now spent more time on this post than on the actual problem
Part 3: Vista SP1 Horror
Well, I had lots more Visual Studio crashes. I even got it down to the point where I could crash it on every build. I decided to uninstall Ankh, which was sad because it's a cool tool (Visual Studio integration for SubVersion). I don't think that's the real root cause, but it does appear that the root cause ricocheted a bullet into Ankh's head that brought VS down. I think the real cause is something horked up in our project somewhere (Bryan is getting some weirdness, too and he is running Server 2008 and VS without SP1).
So, all this to say, I retract blame from Vista SP1. In fact, I was pretty pleased at how smooth the install process was and how it managed its own multiple reboots for multiple updates and such.
So, all this to say, I retract blame from Vista SP1. In fact, I was pretty pleased at how smooth the install process was and how it managed its own multiple reboots for multiple updates and such.
Thursday, September 18, 2008
On the device
Part 2: Vista SP1 Horror
For the love of all that is holy! Well, my fear of Vista SP1 appears to be justified. Visual Studio has crashed four times today in the past two hours. It usually happens during a build. I'm going to keep tabs here of what I do to figure out / fix the problem. My first clue is in the event viewer, I see this error for every VS crash:
Log Name: Application
Source: .NET Runtime
Date: 9/18/2008 3:01:12 PM
Event ID: 1023
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: mylappy
Description:
.NET Runtime version 2.0.50727.3053 - Fatal Execution Engine Error (71027706) (80131506)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1023</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2008-09-18T20:01:12.000Z" />
<EventRecordID>62007</EventRecordID>
<Channel>Application</Channel>
<Computer>bigbird</Computer>
<Security />
</System>
<EventData>
<Data>.NET Runtime version 2.0.50727.3053 - Fatal Execution Engine Error (71027706) (80131506)</Data>
</EventData>
</Event>
Digging this up on the interwebs (Bryan calls it, "Google Kung-Fu") leads me to believe that the .NET 3.5 SP1 is horked. So ... reinstalling that ... If there are no more posts after this, then that did it.
Log Name: Application
Source: .NET Runtime
Date: 9/18/2008 3:01:12 PM
Event ID: 1023
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: mylappy
Description:
.NET Runtime version 2.0.50727.3053 - Fatal Execution Engine Error (71027706) (80131506)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1023</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2008-09-18T20:01:12.000Z" />
<EventRecordID>62007</EventRecordID>
<Channel>Application</Channel>
<Computer>bigbird</Computer>
<Security />
</System>
<EventData>
<Data>.NET Runtime version 2.0.50727.3053 - Fatal Execution Engine Error (71027706) (80131506)</Data>
</EventData>
</Event>
Digging this up on the interwebs (Bryan calls it, "Google Kung-Fu") leads me to believe that the .NET 3.5 SP1 is horked. So ... reinstalling that ... If there are no more posts after this, then that did it.
Goodbye, cruel world
Thursday, September 4, 2008
Reflector and Vista
I just found out that Lutz Roeder sold (or gave or whatever) Reflector to Red Gate. So, I decided to remove my old one and install the new one. I downloaded the .ZIP file from Red Gate and copied it, all nice and pretty, to my Program Files. This is when Vista's security mess started frustrating me. Here's what I did (stripping out the errors from the trial)
1.) Make a shortcut to Reflector.exe, save this to the desktop.
2.) Move the shortcut from the desktop to the start menu items.
Now, I have a handy link in the start menu. However, EVERY time I use the link, I get a security warning. There is a checkbox to permanently disable this warning, but that doesn't work, so ...
3.) Apply this nifty little hack to really disable the security warning.
Done. Sheesh.
1.) Make a shortcut to Reflector.exe, save this to the desktop.
2.) Move the shortcut from the desktop to the start menu items.
Now, I have a handy link in the start menu. However, EVERY time I use the link, I get a security warning. There is a checkbox to permanently disable this warning, but that doesn't work, so ...
3.) Apply this nifty little hack to really disable the security warning.
Done. Sheesh.
Wednesday, September 3, 2008
Back
The past few weeks have been that grinding end of a project. But that's all over. I did learn some things that I might chew on a bit before writing here. However, for the moment, I have a few items of note.
The amateur animator in me must address this item first.
Bill Melendez 1916 - 2008
Even if you have never dreamt of being an animator, you have probably been touched by this genius.
Law of Demeter
Bryan introduced me to this important concept today. Very, very interesting.
Visual Studio Style
I think I posted a while back about darker themes in Visual Studio. I have revisited that to find some better (or updated) themes. A quick Google search brought back this posting on such things. I chose the Ragnorok theme from here.
... OK. That is all for now.
The amateur animator in me must address this item first.
Bill Melendez 1916 - 2008
Even if you have never dreamt of being an animator, you have probably been touched by this genius.
Law of Demeter
Bryan introduced me to this important concept today. Very, very interesting.
Visual Studio Style
I think I posted a while back about darker themes in Visual Studio. I have revisited that to find some better (or updated) themes. A quick Google search brought back this posting on such things. I chose the Ragnorok theme from here.
... OK. That is all for now.
Subscribe to:
Posts (Atom)