May 2009 - Posts
Touching too many pieces at once almost always causes errors and that became evident when I began to see the error of this post’s title. My VS2008 install was missing the asp.net templates and I could not understand why -later on I realized it was because I had not selected a component during the original install-, and tried several suggestions like running devenv.exe /installvstemplates from the command prompt and resetting VS settings in the Import and Export Settings menu.
Long story short, those brought more problems. I just needed to add the component, but now the VS installer would not run. Avoiding a longer delay I attempted to work on an existing project, but then I could not load the Controls Toolbox without facing three more errors now related to SQL components. Running the SQL Repair halted mentioning a VS problem.
I was doomed. OK, I am being dramatic, but it was a drag!
I decided to re-install VS. And what do you know, I couldn’t run the installer. A forced unsinstall was required now. A short search and Aaron Stebner’s blog post came to the rescue.
After uninstalling VS, I re-installed it, ran SP1 and repaired SQL. I am safe again, so I thought I’d save someone else the effort of finding VS Product GUID and post the command to uninstall Visual Studio Team System 2008.
msiexec /x {80C06CCD-7D07-3DB6-86CD-B57B3F0614D8}
If you have a different version, you’ll need to find it. Just read Aaron’s post and follow the steps to get the msiinv tool and obtain a list of installed applications according to msi.
Note: this is not always what you need to do. It was my last resource, so use it when the re-installation of templates does not work, and causes Packages registration to go awry.
If you are like me and try to be environmentally friendly by not burning DVDs unless it’s really necessary, and you prefer to install apps from ISO images, be prepared for this one about VS 2010.
Like many programs that may need to run additional tasks after the first install pass, VS2010 setup will continue after reboot. Make sure you set your ISO reading software to remount the image on the virtual drive after the reboot, it’ll save you from a surprise when the installer can’t find the necessary files to continue.
News about the beta will start sprouting everywhere and I am lucky I already downloaded it. Sadly, I ran out of time and energy to install it. This beta is only available to MSDN subscribers at this time and is not feature complete. I am looking forward at the new TFS features, however the only place where I could find information about them is Brian Harry’s blog. With luck he’ll lead me through them all.
Find the original of this one, the first of a series of posts at my DotnetNuke Blog.
This one mostly happens to newcomers to DotNetNuke development that don’t read, or just do some fast skimming over the instructions for DotNetNuke installation. It doesn’t happen when using the Install package, just with the Source one and will manifest itself when calling the application for the first time from the browser.
The Parser Error Message is vague and specific at the same time, “Could not load type 'DotNetNuke.Common.Global'”. Of course, with some experience, it’s clear that the cause is a missing web.config file.
Look at the Website folder, make a copy of the development.config file and rename it web.config. Then go ahead and install DotNetNuke.
I needed to create a report in a DNN website to obtain the Total billable hours for a single case in Dynamics CRM. All my previous DotNetNuke modules for CRM had been done in VS2005, which lead me to miss a detail. I published the post at my DotNetNuke blog
While reading the preface to the book “A New Kind of Science” (NKS), I was listening to REM’s song “It’s the End of the World as We Know It (And I Feel Fine)” How appropriate to coincide with the official launch of a project of the book’s author, Stephen Wolfram.
I cannot say that I was following this project from the beginning (back in 2000), but I know it is going to generate more news now that it was officially launched yesterday (may 15). This post is a short recap of information that can be found at the project’s website.
The project is called Wolfram/Alpha and it is a computational knowledge engine. With its operations headquarters in Illinois, its objective is to “make all systematic kinowldge immediately accessible and computable for everyone.”
At launch it had more than 10 trillion pieces of data, 50,000 types of algorithms and models and linguistic capability for thousands of domains.
The project is the result of Wolfram’s leadership. To reach this point, after almost 30 years, two previous developments had to take place. Mathematica and NKS.
Mathematica is, according to its own definition, “a computation and visualization system, development environment and deployment engine. Used throughout diverse technical fields, including engineering, science and financial analysis.” Together with NKS, the book that explained the paradigm that made it possible to imagine the very same possibility that Wolfram/Alpha could exist, they are the consequence of the singular vision of this 49 year old ant his Wolfram Research team.
Wolfram/Alpha website claims that the system has the capability to understand free-form input. Presented as both as a technology and a platform, we’ll soon be introduced to developer APIs.
It is indeed a fresh approach to science and knowledge in general. If you want to learn more you can visit its site at http://www.wolframalpha.com. A free online version of NKS can be found at http://www.wolframscience.com/nksonline/toc.html
More Posts