my Computer Quest: Programming

Showing posts with label Programming. Show all posts

14 July, 2014

Code 13EC - error installing VS2010 SP1 Update

Visual Studio (Photo credit: Jonathan Caves)

14-July-2014

For a time and a season, I struggled with this error code, Code 13EC, which is related to the installation of Visual Studio 2010 SP1 Update.

Not that it happens to all computers that carries Visual Studio 2010, but to one, or two.

So it beats me to some confusion, what's wrong?

Try as I will, whenever I have time, the result is the same: Code 13EC, error installing Visual Studio 2010 SP1 Update.

The Best System Optimize Software

If I am not mistaken, whenever there is some update for Windows, this KB is included, and every time, it would fail. What's wrong?

I searched, and found some articles, but none helped. It helped others, but not me.

Then while doing some other updates, which was not coursed through Windows Update, I just thought of 'hitching' this particular update to the batch, which is using MS Web Platform Installer. My guess and trial was backed by my finding the same update when I searched for updates using that particular application.

And... voila!

It worked!

And did I try it on the other computers? You betcha! And it worked also!

So if you are getting Code 13EC, error installing Visual Studio 2010 SP1 Update, try MS Web Platform Installer. It just might be the answer to your problem.

Who knows?

Till then!

19 November, 2013

My mistake: VS2010 to VS2013 is OKAY

Screeshot of FarPoint Spread for Windows Forms version 5 in Visual Studio 2010. (Photo credit: Wikipedia)

19-Nov-13

So I was wrong. I thought that the errors I got from installing Visual Studio 2013 was due to the absence of Visual Studio 2012. I was wrong.

In one of the PCs I tried to install Visual Studio 2013 without Visual Studio 2012. That means I only have Visual Studio 2010. And boy, having these old desktops can cause a lot of confusion sometimes. It did, and I thought that the errors coming up one after another, they were all due to the “jump” from VS2010 to VS2013.

I was wrong.

While installing Visual Studio 2013, some errors came, mostly about SQL-related, and I just either retried the installation (modify or repair), until a restart was mandated. The installation continued after the reboot, until it was fully completed.

I called up VS2013, and when it opened nicely without any hesitation or problem, I was satisfied. When I was able to install updates, it was when I was completely assured that the installation was okay, or that I am able to “jump” from VS2010 to VS2013. I was wrong; dead wrong.

And only after my insatiable curiosity got the better of me did I find out about it, that I was wrong, and now, I am righting that mistake.
Jump from VS2010 to VS2013 is okay; it is possible.

Till then!

03 November, 2013

Don’t jump: VS2010 to VS2013

Image via CrunchBase

1 November 2013

Visual Studio 2010

I have been using Visual Studio 2010 for quite some time now, and seeing Visual Studio 2012 and having some hands-on with this version gave me some inspiration.

So imagine my excitement when I came across Visual Studio 2013! One thing that got me hooked (immediately) is the Code Lens extension. And that is just the extension…

I now continued my reading of Beginning ASP.NET 4.5 in C# and VB eBook, but I decided to use VS2013. I noticed right away that web site project creates 3 files, and the code-behind file, which is only one in previous versions, are now 2: the program code and the designer code.

I thought right away that Visual Studio has something new to offer, so that I started to clean up one other PC that I use for development, sort of back-up.

Clean-up done, where much old data files were discarded, and the disks were resized, and even repartitioned, I salvaged some space for Visual Studio 2013.

Then, I got some errors during the installation. As always the promise, Microsoft will try to fix it.

Retry, same error, same message. Retry, same error, same message. And finally, retry… same error, same message.

I looked (finally, some serious scrutiny) of the packages having error in the installation, and my immediate guess is that these files I do not know, and owing to the very close release dates of Visual Studio 2012 and Visual Studio 2013, I guessed that these files must be from Visual Studio 2012. The other confirming factor to this wild guess is the installer package size – VS2012 has a bigger installer than VS2013.

Visual Studio 2012

I now digressed to installing Visual Studio 2012. As earlier thought, the installation went through without a single glitch.

Setup completed. Product launched. Updates applied. Done!

Visual Studio 2013

Coming back to Visual Studio 2013, the installation was then retried, and this time, there was no error that came up. Setup completed in a jiffy!

Product launched. Updates were installed. And now, I have a back-up machine that runs Visual Studio 2013.

Lesson learnt: Don’t jump (you cannot jump) from Visual Studio 2010 to Visual Studio 2013. Do Visual Studio 2012 first. They have done much in the in-between years…

Till then!

22 August, 2013

XCOPY on paths with space

Xcopy | 17th Feb (3/28) (Photo credit: Rob Hayes.)

22-August-2013

I have missed posting a number of articles, and many things that I should have noted down, I have failed to note down. I would recall that this blog was created with the intent of having my own resource later on, and having it published online, also for others who may be looking for the answer(s) to the same question(s) they have in mind.

I must admit that a lot of the important things that I should have logged down, I have forgotten - now that my web applications are running. And that is, even if I still have the links I to the reference articles and posts from other developers like me. Shame...

So just to break the silence, let me just note this down. And hope it helps many others.

I came across the problem of the need to copy some files to other PCs, and I thought it should be a very normal thing. "Easy," I thought to myself. Well, not so, because the file path of both the source and the destination have spaces. The moment I ran my batch file, I got the error(s).

I searched, "xcopy file path with space", and the top few links, I checked. I got what I wanted. The file path with space is simply needing a double quote enclosure. That is like

C:\Program Files

becoming

"C:\Program Files"

and all other definitions or switches remain the same.

Very simple solution, isn't it?

I should now say, till then!

Reference:
using XCOPY when directory has a space in name

05 December, 2011

When SxecuteScalar() returns null

The Greek lowercase omega (ω) character is use...

Image via Wikipedia

05-Dec-2011

I was working on a new web page today, and I decided to use ExecuteScalar() as my method to fetch a singular data that returns a string.

I completed the whole code, and during debugging, I encountered some issues. One of them is simply throwing an exception, and when I stepped through, I found that it was due to a null value being returned by the ExecuteScalar() procedure.

I then checked from the web on possible solutions to this problem, and after putting in all the patches, all scenarios can now be handled.

Here’s how it works. Detect first if the return value is null, then handle it appropriately:

if (cmd.ExecuteScalar() == null)

{

}

An else clause is then added to handle possible return values other than null:

else

{

bfrResult = cmd.ExecuteScalar().ToString();

}

And that’s all there is to it. Hope that this helps you also, as it did me.

Till then!

11 November, 2011

Troubleshooting WebSite publishing in Windows 7

Image via Wikipedia11-Nov-2011

This is how I found out about the 'BIG' difference between 'COPYING' and 'COMPILING' when publishing a web site, in Windows 7.

Follow deployment tutorial from MSDN (compiled web site, published locally)
Error: ASP.NET 4.0 application error: Unrecognized attribute 'targetFramework'...
Change IIS DefaultAppPool .NET Framework Version to "4.xxx".
Error: HTTP Error 500.21 - Internal Server Error
Run "%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i". This is to correct installation of ASP.NET
Error: none; website is displayed correctly, and working.

NOTE: \Framework\vN.xxx\ -> this is according to the version that is installed in your computer.
Check from the following folder: C:\Windows\Microsoft.NET\Framework\

I hope that this will be of help to many developers like me who struggles with using the latest technologies, but get stuck somewhere in the middle, one way or another...

Till then!

my Computer Quest

14 July, 2014

Code 13EC - error installing VS2010 SP1 Update