Here’s another reason why smoking is bad (as if we need more reasons). I was out walking my dog, and I always walk past a city bus stop. Each day I walk by and am amazed at the number of extinguished cigarette butts people stuff in the sign post (through the holes) as they put their smoke out before getting on the bus. Apparently, when you stuff a lot of flammable objects into a tightly contained area with exposure to a constant flow of oxygen and you introduce something burning it catches fire!
A lady driving by stopped and stared in amazment, asking me if it was a metal post on fire. I told her yeah, some genius put his cigarette out in the post. I ran to get water from my place (around the corner), came back with a quart of water in two sport bottles, and by this time flames were coming out of the post. I started to saturate the fire, and it was so hot you could hear sizzling, and at some point the tip of my bottle got so close to the metal post it started to melt! I used both pints (1 qt) of water to ensure it was completely saturated. Couldn’t stir it up to get the hot spots…because it’s IN THE METAL POST.
Come on people…if you have to smoke, crush it out in the street or on the bottom of your shoe. Don’t put it out in a post ON THE GRASS!
What? I just get a new dev laptop (yeah, pretty proud myself, HP Pavilion dv7, triple-core i5, 6GB RAM, 640GB HD, 17.3″ display…) and I install VS 2008 and 2010, SQL, etc. Start working on an existing website using VS 2008 and it says “Visual Studio language support for C# is not installed. Code-editing Intellisense will not be available. Markup Intellisense for server controls may not work”. You gotta be kidding me…
So I hit the googleverse and attempt to find a solution, since I know I’m not the only one who’s ever seen this before. One site discusses a guy who completely removed all things Microsoft, reinstalled everything and it worked……seriously? Finally happened to find this one”, thankfully! Post is a year old but was entirely helpful!
All I did was close VS 2008, open a run prompt and type devenv /resetskippkgs and hit enter. VS 2008 opens and everything appears fine, but Intellisense is still missing.
I opened it in VS 2010 and Intellisense is fine. I learned my lesson about hanging on to old technology…
I’ve been tasked with designing the end-user side of SCSM at our company, including building the web page users will use to submit helpdesk tickets and build the workflows behind the scenes. So I went to install the SCSM Authoring Tool on my Windows 7 box, and every time it would break in the same spot, telling me “VS Shell 2008 SP1 is not installed”. I followed the prerequisite list exactly and in order, yet it still told me this, even after rebooting. The solution? Thanks to HuguesDePayns’s posting on TechNet, it finally worked. Here’s what had to be done:
First, run the VS Shell 2008 SP1 installer found in SCSM_AuthoringTool_2010_SP1CDImagePrerequisitesVS2K8Shellenvs_shell_isolated.exe
When that’s finished, open a command prompt (as administrator) and enter the following command:
msiexec /i “CDImageSetupAuthoringTool.msi”
It runs quietly, showing the status as it goes, then suddenly it will stop. If there are no error messages, it’s installed, and you’ll see it in your Program Files under Microsoft System Center.
Here’s the new home of The Nullable Type! Eventually I’ll move all of my old posts over here from Blogger, and all new posts will happen here.
I ran across a discussion online today (can’t recall where it was, unfortunately) that mentioned what to do when you put a SharePoint web part (2007 or higher) on a site and it breaks, or the web part itself is faulty. You’ll usually get an error page that you can’t get past. The solution is rather easy…append “?Contents=1” to the end of the site url. For example, if your site that you put the web part on is “http://server/path/site/subsite/SitePages/Home.aspx”, your new URL will look like this:
You’ll be taken to the Web Part Page Management page for that site, where you can remove the selected web part and restore the page’s functionality.