Friday, November 28, 2014
Hyper-V doesn’t block installing Windows Technical Preview 9879 on Surface Pro 3

Since WTP has the nice ‘feature’ of auto-installing updates, now that 9879 is on the slow band of updates, every day or two, it attempts to update from 9860, which closes whatever I am working on, and then fails.  Super.

So, on the off-chance that it was Hyper-V that was causing the issue, I uninstalled it and tried the update myself.  No luck.

Still with an obscure error message:

Failed execution of queue item Installer: ServiceModelReg Installer ({79675b3f-2054-4efd-aa9d-e1830916be47}) with HRESULT HRESULT_FROM_WIN32(52).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed

posted @ Friday, November 28, 2014 12:13 AM | Feedback (0)
Tuesday, November 25, 2014
About those new Windows Technical Preview 9879 iso files




posted @ Tuesday, November 25, 2014 1:32 PM | Feedback (0)
Monday, November 24, 2014
Web Essentials 2015 – Missing .scss support?

It took me a few minutes to realize this, but it appears that even though there is a Web Essentials 2015 release (which may or may not have been configured originally with Visual Studio 2014 RC), it doesn’t appear to rebuild the .css file when you make a change in the parent .scss file.  I’m assuming this will be fixed soon.

VisualStudio Gallery appears to be down (only getting 500 errors), so I can’t check there at the moment.

posted @ Monday, November 24, 2014 10:14 AM | Feedback (0)
Still can’t run WTP 9879 on Surface Pro 3

As part of the Windows Technical Preview program, you don’t have total control over whether or not Windows will try to update to any newly released builds if and when they become available.  I thought I had switched to the ‘slow’ build mode, but apparently not, as every couple of days, it tries to update from 9860 to 9879 and fails.

I have read online that other people have been able to, so I’m not sure why my Surface can’t.  My guess, based on random things I’ve read, is that it is because of Hyper-V, which I don’t want to uninstall (even though I’m not really using it at the moment) because it will likely break Visual Studio 2015 Preview (some of the new Android development software relies on it).  I have some vaguely confirming evidence of this because I was able to load 9879 on my MacBook Air after starting from scratch and loading VS 2015 P after 9879.

Supposedly, they are ‘fixing’ 9879 before releasing it to ‘Slow’ build mode because of other issues with the OS, but if it requires you to install it and then do the fixes, I don’t know that there’s much I can do unless/until the next build in January.

posted @ Monday, November 24, 2014 9:39 AM | Feedback (0)
Thursday, November 20, 2014
Nuget still sucks – Visual Studio 2015 Preview version

Why doesn’t Nuget just work?

I have a solution.  It’s mostly ‘shell’ projects as I’m just starting out.  About the only package installed is EF 6.1.1.  It builds just fine (on an existing machine with VS 2015 Preview installed).

I check it into TFS.  I go to a new machine, with VS 2015 Preview installed.  I connect to TFS, I download from source, I go to build…..of course, it fails.

I check in options to see if it is configured to automatically download packages.  Of course it is.

I right-click on the solution….no longer is there an option to tell it to enable Nuget restore (since Nuget is so stupid, you have to tell it twice) and I see no such option in the new, nearly useless, window to manage packages, where it says, of course, that EF is already installed. 

I do not want to click on anything to manually reinstall EF.  I want it to do what it should know to do, see that a configured package is not actually downloaded on this machine, and download the damn things, and build the solution out of the goddamn box they way it goddamn should.

Why doesn’t Nuget just work?

posted @ Thursday, November 20, 2014 11:39 PM | Feedback (1)
Wednesday, November 19, 2014
Does Windows Technical Preview 10 block Surface Pro 3 Firmware updates?

I haven’t read that it does, but I never received notification through Windows Update that the October update was available, and now that the November update is available, I don’t see that one either.

I check here for the whole kit and caboodle and install them manually, but still….

posted @ Wednesday, November 19, 2014 2:46 PM | Feedback (0)
Tuesday, November 18, 2014
An old school way of writing application code

In this case, ‘old school’ means ‘generally bad’.

Now, in certain circles, one can’t swing a dead cat and not hit someone who thinks that stored procedures are evil.  Yawn, yawn, yawn.  No, they aren’t, get over it (having said that, you should rarely use them, as there is almost always a better way of doing things).

That being said, if you are going to write stored procedures, you almost definitely shouldn’t do them this way.  The mixing of insert/query/update code, the ’magic number’ error codes, the convoluted parameter checking, and this isn’t even an example that actually has any meaningful business logic (not at least as I define the term) whatsoever.

Don’t do this, please.

posted @ Tuesday, November 18, 2014 12:20 PM | Feedback (0)
Saturday, November 15, 2014
Adobe Brackets

This is…..intriguing.

Ostensibly, this is a code editor for web development, but (somewhat by accident) I managed to open up a SQL file, C# file and text file in it, and there is some syntax highlighting, etc. that comes along.

Not that I think it will replace Notepad or anything, but it’s interesting.

posted @ Saturday, November 15, 2014 12:59 PM | Feedback (0)
Friday, November 14, 2014
Rerunning Visual Studio 2015 Preview Secondary Installer

Did you have a problem running the Secondary Installer when installing Visual Studio 2015?  I did (something went wrong with the node.js download and install).  So, how do you rerun the thing?  Run the secondaryInstaller.msi from the ISO?  Nope.

Instead, go to C:\Program Files (x86)\Microsoft Visual Studio 14.0\SecondaryInstaller and run SecondaryInstaller.exe from there.  I assume it will be in regular Program Files if you have an x86 machine, but since I don’t, I can’t verify that, it’s just a guess.


posted @ Friday, November 14, 2014 10:36 PM | Feedback (2)
How Chocolatey saved Windows

Apparently, automation and package management saved Windows from going out of business.  Um…..what?

posted @ Friday, November 14, 2014 11:23 AM | Feedback (0)