Showing posts with label Visual Studio 2010. Show all posts
Showing posts with label Visual Studio 2010. Show all posts

14 July, 2014

Code 13EC - error installing VS2010 SP1 Update

Visual Studio
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...
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!
Enhanced by Zemanta

03 November, 2013

Don’t jump: VS2010 to VS2013

Image representing Microsoft as depicted in Cr...
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!

Enhanced by Zemanta

01 February, 2013

Azure hijacked my VS2010 Publish Web dialog window

Image representing Microsoft Azure as depicted...
Image via CrunchBase
01-Feb-2013

Around Wednesday of last week, I got to check on what could be new to me on the Web Development arena. I mean, I haven’t been keeping up lately with the latest releases, and so what could have been out in the world for some time, maybe a year or so already, will be new to me, since these would be my first time to encounter them.

I am reading on one book, Beginning ASP.NET 4.5 in C# and VB, and I saw that one thing I have been seeing, but keep on ignoring, is Azure – and it was mentioned in that book.

It took my curiosity by the hand, and I just found myself installing here and there.

That’s when my problem started... VS2010 Publish Web calls Azure dialog...

I was just happy finishing all of my installation, and since these are add-ons, or plug-ins, I couldn’t immediately “see” the effect of what I have just done.

When I went back to my codes using VS2010, opened up one web application, made some minor changes, and tried to publish it, lo and behold! The Publish Web Dialog Window is now an Azure dialog box, telling me to publish on Azure, and as I found out, the only way to make a publication is either by logging in with an existing account, or by creating a new one. What?!

I got these installed, by the way: Visual Studio 2010 Ultimate, used for some time already, Microsoft Visual Studio Express 2012 for Windows Desktop, recent but not so recent, and Microsoft Visual Studio Express 2012 for Web.

I am very sure that having installed the Express 2012 IDEs did not give me the problem, but I doubted that suddenly.

Troubleshooting

First thing I checked is my list of installed programs, and as I expected, and was happy enough to confirm my initial guess, is that “some” Azure programs kicked in, by design, since Azure is supposed to, I believe, be taking over some of Visual Studio’s dialog boxes and windows (Now is that right? Is my understanding right? Am I making any sense at all?) So what I did first is to uninstall these Azure programs, as selected by date of installation. I thought I was done, and things will be back to normal.
It didn’t – I still see the Azure dialog window when doing a Publish Web in VS2010.

Along with the bunch of Azure products installed in the past few days were some updates to VS2010, and even Windows itself. So I carefully checked on the list, and selected those that I think were add-ons, and uninstalled them as well.

Nope, that didn’t help; still got the problem when doing a Web Publish act.

As I needed to apply the changes I made, I have to make a choice by making a “synchronize” move, copying the modified code to the other PCs I use, and doing a web publish on these production machines. Thankfully, the change done was okay, and no untoward side effect was observed or reported.

Back to my problem: I thought that if I would uninstall VS2010, and do a reinstall, maybe that would do the trick. So that is what I did. Went through the time-consuming process of uninstalling Visual Studio 2010 Ultimate, and hey, it was fast, cause only 2 items were uninstalled. Maybe nothing was left after the previous uninstallation... think so?

I restarted my machine, and went right away to reinstalling the Visual Studio 2010 suite. When it was done, I clicked on the shortcut, applied the license key, and then called up the web application. I went straight to publishing the web – and lo and behold! I would like to pull out all my hairs!

Nah, I still have the problem!

I couldn’t believe that a week has come and gone, and I was trying to solve one small problem, but I couldn’t fix it. I was thinking, I was making this troubleshooting skill of mine an asset in my job applications, but here I am, doing one simple problem, and I’m going nowhere, getting nothing done. Just running around in circles, to say the least.

Then yesterday, out of desperation, I wondered whether taking out all of the Visual Studio programs would somehow be the solution to my problem.

Well, that wondering led to doing, and since I have to go home for some urgent errand (my 2nd daughter had a high fever while in school, so I had to leave work at noon and filed that as an urgent leave of absence), I brought along my laptop, and around past 3pm, when we got home, I opened my laptop to execute the complete uninstallation of *Visual Studio*.

That took some time, especially that I had to attend to some other things here and there, and we had to eat dinner, and I have to look after the youngest while my wife looked  after our sick child – time flew so swiftly and it was night all of a sudden without my knowing it... I should say, without my noticing it...

That was last night. And while I was uninstalling the Visual Studio suites from my laptop, I have another desktop PC back in the office that I am working on, and since the desktop PC is an older model, making it the slower unit, and a fresh install at that, I said, why not I make this somehow the control unit, and find out, to confirm, that it is the Azure products, and not the Visual Studio Express 2012 products, that gave me the problem? Anyway, it would be the same steps that I will take:

Install Visual Studio 2010
Install Visual Studio Express 2012 for Windows Desktop
Install Visual Studio Express 2012 for Web

The VS2010 should come first, followed by either the Web or Windows Desktop version.

So I worked on the 2 machines simultaneously, the desktop PC back in the office I’m doing remotely, while the laptop is with me at home.

True enough, installing Visual Studio 2010 first and foremost gave me back the original Publish Web dialog window. True for both desktop and laptop PCs.

I then installed Visual Studio Express 2012 for Windows Desktop. When it was done, I opened up VS2010, called up the web application, invoked Publish Web command, and I got the same dialog window.

Confirmed, it is not the VS Express 2012 for Windows Desktop that caused the problem.

As a last step, I proceeded to install Visual Studio Express 2012 for Web, and when it was done, I opened up VS2010, called up the web application, invoked Publish Web command, and I still got the same, original, unaltered, Publish Web Dialog Window – 2 weeks ago was “hijacked” by Azure.

I’m back in business!

And with that, I end my recollection of my past 2 weeks’ adventure in software development.

Till then!

Enhanced by Zemanta

18 October, 2011

Domino 6.5 ain't runnin' in Windows 7 (Laptop)

Latitude "Notebook"Image by Annie Mole via FlickrHP ProBook 4430s - Right SilverImage by HP PSG APJ via Flickr
I basically stopped posting articles on my blogs for a variety of reasons.

Sometime in early September, I was issued a laptop, an HP ProBook 4430s, so that they can take away my old desktop - hey, that what I was told!

And I was in the heat of installing and tweaking and customizing things, when after so many tries, I have given up: Domino 6.5 breaks in Windows 7 (laptop).

I know, a couple of weeks earlier to my getting a laptop, I was bragging about making Domino 6.5 work in Windows 7 (Windows 7 and Lotus Domino 6.5) - which is althemore, on an old Dell desktop PC. I didn't knew that it would all be completely different with a laptop. Took me almost a week of doing with the laptop what I did with the desktop to make Domino 6.5 work, but success eluded me everytime.

When I reached the end of my rope, after about 2 weeks, even trying out Domino 8.xx, I told my boss - the laptop I have no use for it, since the major programs I am maintaining is running with Domino 6.5 - which doesn't run.

Basically, Domino 6.5 is "seen" by Visual Studio 2005 and Visual Studio 2010. It can be called in. It can be referenced. But when I run the code, I get "null" errors, indicating that the object has not been instantiated.

Now in our company, we are issued either an HP machine, or a Dell counterpart. Another member of our team also got a laptop, and it was getting ready for deployment (meaning, to be used by the user, whose old desktop will also be taken away...), so my boss made a proposal.

Can I try it out on the other laptop? Maybe it was brand-sensitive, or maybe.... what?

Anyway, I yielded - that is what I was already thinking of doing a week after the unsuccessful tests - and the would-be owner agreed.

I tried, and guess what? The same error I got! So whether it is an HP ProBook 4430s, or a Dell Latitude E5420, if it is running in Windows 7, Domino 6.5 can't run. That's for my case.

As for the old Dell desktop PC, a dying GX280, which I got to reformat and reinstall Windows 7 Enterprise edition, 32-bit OS, I was able to apply the whole fix that I documented weeks back, and Domino 6.5 is able to run. So it's all on the laptops, I suppose... eh?

These are the specs, to be more precise:
Windows 7 Enterprise edition, 32-bit (64-bit ain't the right fit yet, dude!)
> desktops, laptops, they all get the same OS

And the very reason why we can't use 64-bit OS, is that we are still running Oracle 8i systems! And the upgrade isn't a time within reach, my man.

Finally, 64-bit ain't no use, since we only have 4GB RAM in our machines. I just made a good alternative to Windows 7, speeding up my processes by employing Readyboost - 2 pieces of 8GB thumbdrives plugged into my new laptop - now that's something!

The grapes are not so sour after all...