Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesDatabase Driven Unit Testing MVC C# after upgrading to DNN7 & DnnDev.meDatabase Driven Unit Testing MVC C# after upgrading to DNN7 & DnnDev.me
Previous
 
Next
New Post
11/2/2015 11:22 AM
 

I am getting an error running just the Database Driven units test of my existing project after I upgraded to DNN7.2, VS 2013, & localtest.me (resolved to 127.0.0.1) from Local Host, DNN 7, VS2010.  It was all working before.  Now this is the error I get running the test running as administrator:

Result Message:    The URL specified ('http://dnndev.localtest.me/') does not correspond to a valid directory. Tests configured to run in ASP.NET in IIS require a valid directory to exist for the URL. The URL may be invalid or may not point to a valid Web application.

 My site loads find in the browser on http://dnndev.localtest.me.  I have scanned the web for any issues related to this and everything they say could be wrong does not seem to apply to my situation.  I have a production install that is delayed over 1.5 months because I can not unit test it.

 

Sample:

        [TestMethod()]
        [HostType("ASP.NET")]
        [UrlToTest("http://dnndev.localtest.me/")]
        public void DoPayPalRecurringPaymentSuccessTest01()
        { ... }

 

DNN Modules are compiled as ASP.Net v4.0 with start URL as 'http://dnndev.localtest.me/' with a project URL for each module as 'http://dnndev.localtest.me/desktopmodules/QHWeb/xxxxxx' where xxxxxx is the module name.  All have had virtual directories created using VS and confirmed in IIS.  They are set for Override Application root URL in VS as 'http://dnndev.localtest.me/'

 Hosts File: (No related entries)

IIS Bindings: dnndev.localtest.me 80 *

DNN Aliases: dnndev.localtest.me

IIS Physical Path: C:\Websites\dnndev

IIS AppPool: dnndev (as v4.0 as Integrated)

Event Log: Empty - Gives no indication of errors of any kind from anywhere for months.

C:\Websites\dnndev Security: NETWORK SERVICE, Administrator, dnndev all have full control

I can supply any addition information you request.  I am in dire need of resolving this issue, and since this has never been solved before, it will help others who have the same issue.  I am open for offline conversations as well to help resolve this.  I am desperate. I have bugs in production, I can not fix because I can not test.

 
New Post
11/2/2015 2:26 PM
 

Solved: When upgrading from IIS6 to IIS7+, IIS backwards compatibility was lost.  The Unit testing appears to require it (IIS6). 

The event log was in fact containing errors stating it could not access the metabase data.  The solution was found at this link:

http://blogs.msdn.com/b/profiler/archive/2010/07/23/tip-fixing-vsperfaspnetcmd-metabase-errors.aspx

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesDatabase Driven Unit Testing MVC C# after upgrading to DNN7 & DnnDev.meDatabase Driven Unit Testing MVC C# after upgrading to DNN7 & DnnDev.me


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out