Wednesday, September 08, 2010
  Search
 
Register
Login
 
Customize Google Analytics for DotNetNuke Search
You can easily set up your Google Analytics account to track the search feature on your DotNetNuke website and take advantage of all the in depth reporting that Google has to offer. It's simple, here...

Find this article and more in the category

Read This Article . . .

Creating a Virtual Directory in IIS
One of the first things you will need to do prior to installing DotNetNuke on a server is to create a virtual directory which will host your DotNetNuke website.  If you have full control over you...

Find this article and more in the IIS & ASP.NET category

Read This Article . . .

How to Use the DNNLabelEdit Control
 It's easy to use the DNNLabelEdit control, you know the one you mouse over and edit in place? Yeah, that one. In just a few minutes, you can begin using the control on your sites as well for full on...

Find this article and more in the Module Development category

Read This Article . . .

Setting Up the DotNetNuke Side of Multi-Websites
Ok, so by now you know that DotNetNuke can handle multiple websites, but you still want to know why. Well, it’s pretty easy once you know how to do it, but it can be pretty confusing to some who are ...

Find this article and more in the category

Read This Article . . .

Using DNN to take Advantage of GoDaddy Domain Names
Let's face it, GoDaddy is cheap. Pay for the hosting services and the domain names are $1.99, not a bad deal. And even without hosting services, you can pick up domain names for as low as $6.99. Put ...

Find this article and more in the category

Read This Article . . .

DotNetNuke 5 Cambrian Extropy Skin Features and Limitations
The new DotNetNuke Extropy skin looks very cool from a distance...leaps and bounds above the old default blue skin. But, it's got some limitations you should know about upfront.

Find this article and more in the category

Read This Article . . .

Converting a CSS Template To a DotNetNuke Skin
Creating DotNetNuke Skins can be a time consuming task. But, it's really not that hard and it doesn't have to be if you can use templates to help get started. Why not convert some free templates from...

Find this article and more in the category

Read This Article . . .

More Ways to Install DotNetNuke Modules with the URL Method
While DotNetNuke has a built in mechanism for installing modules, there is another method you can use as well. This is a great alternative to use especially when you are trying to install larger mod...

Find this article and more in the category

Read This Article . . .

Generate a Module Data Access Layer With CodeSmith
With the introduction of some of the newer DNN tools, building a custom module is becoming more and more easy. With the right tools, you can have a custom module built in no time flat. This will outl...

Find this article and more in the DotNetNuke category

Read This Article . . .

Setting Up Multiple Websites
You can create multiple distinct, (mainly) independent websites with one instance of a DNN installation on your web account. In lamens terms, this means that you can purchase ONE web hosting accoun...

Find this article and more in the category

Read This Article . . .

Search for Articles

Virtual-Essential's DotNetNuke, .NET, and SQL Tips For the Developer

Minimize
Feb 6

Written by: Briana Tarrance
2/6/2008 10:54 PM 

Recently, I was working in the a solution that I had been working on for the last several days and received this error when I tried to compile the application:

The project file ' ' has been renamed or is no longer in the solution

I had been loading and unloading other projects around the same time, but nothing happened (as far as I am aware) to the particular project that I was trying to build now.

Here's the Scenario & Resolution

I have a solution with 4 projects in it and I went through the properties of each project looking specifically at the references for each. What I am looking for are references to any assemblies that are no longer valid.

When I reached my web ap, I found that I did indeed have one assembly displayed in the list marked as unavailable:  assemblyname.dll (unavailable). I removed the reference and began immediately compiling again.

All in all, total downtime resulting from this issues was about 40 minutes....YUCK! Hopefully, you're able to get back on track much quicker. Good luck.

Thanks to Michiel Van Otegem' s site  for getting me back on track

Tags:

Your name:
Your email:
(Optional) Email used only to show Gravatar.
Your website:
Title:
Comment:
Security Code
Enter the code shown above in the box below
Add Comment   Cancel 
 
 
Copyright 2008 by Virtual-Essentials.com Privacy Statement    Terms Of Use