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 ExtensionsModulesModulesMy First New Module - Tested OK - But VB Files missing in Production!My First New Module - Tested OK - But VB Files missing in Production!
Previous
 
Next
New Post
4/16/2010 8:45 PM
 

Greetings,

  I really need your help.  I have spent over a week trying to chase this issue down.  I have written a very basic hello world module using a database,  I am using VS 2008 Pro and compile what should be a WAP for the module (because it has vbproj files).   I have tested, bebugged and proven the module; but when I install it into production my my real webserver, it complains that the ascx.vb files are missing for my view module (probably all three View, Edit, Settings).  I have another module compiling the same way but without this issue going into production.  I have compared DNN files, vbproj files, source code without success as to why one of the modules does not work.  So, I finally took the working module directoy and manually installed the code from my non-working moduel; and it now too is failing in production complaining of missing vb files.

If I physically remove my vb files from my test DesktopModules subdirectory, it fails in test too.  If I remove the VB files from the working module, it continues to work.  Again, I have compared and looked for everything through the DNN files, vbproj files, source code, includes, debug compile; and I can't figure this out.   Please help!?

Error: T is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: The file '/DotNetNuke/DesktopModules/QHWeb.Terminology/ViewTerminology.ascx.vb' does not exist. ---> System.Web.HttpParseException: The file '/DotNetNuke/DesktopModules/QHWeb.Terminology/ViewTerminology.ascx.vb' does not exist. ---> System.Web.HttpParseException: The file '/DotNetNuke/DesktopModules/QHWeb.Terminology/ViewTerminology.ascx.vb' does not exist. ---> System.Web.HttpException: The file '/DotNetNuke/DesktopModules/QHWeb.Terminology/ViewTerminology.ascx.vb' does not exist. at System.Web.UI.Util.CheckVirtualFileExists(VirtualPath virtualPath) at System.Web.UI.TemplateParser.ProcessCodeFile(VirtualPath codeFileVirtualPath) at System.Web.UI.TemplateParser.ProcessMainDirectiveAttribute(String deviceName, String name, String value, IDictionary parseData) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ProcessException(Exception ex) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseReader(StreamReader reader, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseInternal() at System.Web.UI.TemplateParser.Parse() at System.Web.UI.TemplateParser.Parse(ICollection referencedAssemblies, VirtualPath virtualPath) at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---

 
The vbproj file:

<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/develope..." ToolsVersion="3.5">
  <PropertyGroup>
    <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
    <Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform>
    <ProductVersion>9.0.21022</ProductVersion>
    <SchemaVersion>2.0</SchemaVersion>
    <ProjectGuid>{314C5798-BA49-450E-9E1F-7DBBA8AF765D}</ProjectGuid>
    <ProjectTypeGuids>{349c5851-65df-11da-9384-00065b846f21};{F184B08F-C81C-45F6-A57F-5ABD9991F28F}</ProjectTypeGuids>
    <OutputType>Library</OutputType>
    <RootNamespace>
    </RootNamespace>
    <AssemblyName>Terminology</AssemblyName>
    <FileUpgradeFlags>
    </FileUpgradeFlags>
    <OldToolsVersion>2.0</OldToolsVersion>
    <OptionExplicit>On</OptionExplicit>
    <OptionCompare>Binary</OptionCompare>
    <OptionStrict>Off</OptionStrict>
    <OptionInfer>On</OptionInfer>
    <UpgradeBackupLocation>
    </UpgradeBackupLocation>
  </PropertyGroup>
  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
    <DebugSymbols>true</DebugSymbols>
    <DebugType>full</DebugType>
    <DefineDebug>true</DefineDebug>
    <DefineTrace>true</DefineTrace>
    <OutputPath>..\..\bin\</OutputPath>
    <DocumentationFile>Terminology.xml</DocumentationFile>
    <NoWarn>42016,41999,42017,42018,42019,42032,42036,42020,42021,42022</NoWarn>
  </PropertyGroup>
  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
    <DebugType>pdbonly</DebugType>
    <DefineDebug>false</DefineDebug>
    <DefineTrace>true</DefineTrace>
    <Optimize>true</Optimize>
    <OutputPath>..\..\bin\</OutputPath>
    <DocumentationFile>Terminology.xml</DocumentationFile>
    <NoWarn>42016,41999,42017,42018,42019,42032,42036,42020,42021,42022</NoWarn>
  </PropertyGroup>
  <ItemGroup>
    <Reference Include="DotNetNuke, Version=5.3.1.7, Culture=neutral, processorArchitecture=MSIL" />
    <Reference Include="Microsoft.ApplicationBlocks.Data, Version=2.0.0.0, Culture=neutral">
      <SpecificVersion>False</SpecificVersion>
      <HintPath>..\..\bin\Microsoft.ApplicationBlocks.Data.dll</HintPath>
      <Private>False</Private>
    </Reference>
    <Reference Include="System" />
    <Reference Include="System.Data" />
    <Reference Include="System.Drawing" />
    <Reference Include="System.Web" />
    <Reference Include="System.Xml" />
    <Reference Include="System.Configuration" />
    <Reference Include="System.Web.Services" />
    <Reference Include="System.EnterpriseServices" />
    <Reference Include="System.Web.Mobile" />
  </ItemGroup>
  <ItemGroup>
    <Import Include="DotNetNuke" />
    <Import Include="DotNetNuke.Common" />
    <Import Include="DotNetNuke.Common.Utilities" />
    <Import Include="DotNetNuke.Data" />
    <Import Include="DotNetNuke.Entities" />
    <Import Include="DotNetNuke.Entities.Tabs" />
    <Import Include="DotNetNuke.Framework" />
    <Import Include="DotNetNuke.Modules" />
    <Import Include="DotNetNuke.Security" />
    <Import Include="DotNetNuke.Services" />
    <Import Include="DotNetNuke.Services.Exceptions" />
    <Import Include="DotNetNuke.Services.Localization" />
    <Import Include="DotNetNuke.UI" />
    <Import Include="Microsoft.VisualBasic" />
    <Import Include="System" />
    <Import Include="System.Collections" />
    <Import Include="System.Collections.Generic" />
    <Import Include="System.Data" />
    <Import Include="System.Diagnostics" />
    <Import Include="System.Collections.Specialized" />
    <Import Include="System.Configuration" />
    <Import Include="System.Text" />
    <Import Include="System.Text.RegularExpressions" />
    <Import Include="System.Web" />
    <Import Include="System.Web.Caching" />
    <Import Include="System.Web.SessionState" />
    <Import Include="System.Web.Security" />
    <Import Include="System.Web.Profile" />
    <Import Include="System.Web.UI" />
    <Import Include="System.Web.UI.WebControls" />
    <Import Include="System.Web.UI.WebControls.WebParts" />
    <Import Include="System.Web.UI.HtmlControls" />
  </ItemGroup>
  <ItemGroup>
    <Compile Include="Components\DataProvider.vb" />
    <Compile Include="Components\TerminologyController.vb" />
    <Compile Include="Components\TerminologyInfo.vb" />
    <Compile Include="Components\SqlDataProvider.vb" />
    <Compile Include="EditTerminology.ascx.designer.vb">
      <DependentUpon>EditTerminology.ascx</DependentUpon>
    </Compile>
    <Compile Include="EditTerminology.ascx.vb">
      <DependentUpon>EditTerminology.ascx</DependentUpon>
      <SubType>ASPXCodeBehind</SubType>
    </Compile>
    <Compile Include="Settings.ascx.designer.vb">
      <DependentUpon>Settings.ascx</DependentUpon>
    </Compile>
    <Compile Include="Settings.ascx.vb">
      <DependentUpon>Settings.ascx</DependentUpon>
      <SubType>ASPXCodeBehind</SubType>
    </Compile>
    <Compile Include="ViewTerminology.ascx.designer.vb">
      <DependentUpon>ViewTerminology.ascx</DependentUpon>
    </Compile>
    <Compile Include="ViewTerminology.ascx.vb">
      <DependentUpon>ViewTerminology.ascx</DependentUpon>
      <SubType>ASPXCodeBehind</SubType>
    </Compile>
  </ItemGroup>
  <ItemGroup>
    <None Include="App_LocalResources\EditTerminology.ascx.resx">
      <SubType>Designer</SubType>
    </None>
    <None Include="App_LocalResources\Settings.ascx.resx">
      <SubType>Designer</SubType>
    </None>
    <None Include="App_LocalResources\ViewTerminology.ascx.resx">
      <SubType>Designer</SubType>
    </None>
    <None Include="01.00.00.SqlDataProvider" />
    <None Include="Terminology.dnn" />
    <None Include="Uninstall.SqlDataProvider" />
  </ItemGroup>
  <ItemGroup>
    <Content Include="Documentation\Documentation.css" />
    <Content Include="Documentation\Documentation.html" />
    <Content Include="Documentation\logo.gif" />
    <Content Include="EditTerminology.ascx" />
    <Content Include="Settings.ascx" />
    <Content Include="ViewTerminology.ascx" />
  </ItemGroup>
  <ItemGroup>
    <Folder Include="My Project\" />
  </ItemGroup>
  <Import Project="$(MSBuildBinPath)\Microsoft.VisualBasic.targets" />
  <Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v9.0\WebApplications\Microsoft.WebApplication.targets" Condition="" />
  <ProjectExtensions>
    <VisualStudio>
      <FlavorProperties GUID="{349c5851-65df-11da-9384-00065b846f21}">
        <WebProjectProperties>
          <UseIIS>True</UseIIS>
          <AutoAssignPort>True</AutoAssignPort>
          <DevelopmentServerPort>62597</DevelopmentServerPort>
          <DevelopmentServerVPath>/</DevelopmentServerVPath>
          <IISUrl>http://localhost/dotnetnuke/DesktopModules/QHWeb.Terminology</IISUrl>
          <OverrideIISAppRootUrl>True</OverrideIISAppRootUrl>
          <IISAppRootUrl>http://localhost/dotnetnuke</IISAppRootUrl>
          <NTLMAuthentication>False</NTLMAuthentication>
          <SaveServerSettingsInUserFile>False</SaveServerSettingsInUserFile>
        </WebProjectProperties>
      </FlavorProperties>
    </VisualStudio>
  </ProjectExtensions>
  <PropertyGroup>
    <PostBuildEvent>
    </PostBuildEvent>
  </PropertyGroup>
</Project>

 

 
New Post
4/17/2010 1:22 AM
 

A "WAP" module doesn't require vb files to run, only for development and compilation. The contents of these .vb files (in WAP) are what get included in the built assembly (YourModule.dll) which needs to be in the website's root bin directory.  My guess is your ascx file uses "CodeFile=" instead of "CodeBehind=" in your first line of source view of the ascx. 

WSP Module: <%@ Control language="vb" CodeFile="EditActivity.ascx.vb" AutoEventWireup="false" Explicit="True" Inherits="Namespace.Community.EditActivity" %>

WAP Module: <%@ Control language="vb" CodeBehind="EditActivity.ascx.vb" AutoEventWireup="false" Explicit="True" Inherits="Namespace.Community.EditActivity" %>


Chris Paterra

Get direct answers to your questions in the Community Exchange.
 
New Post
4/17/2010 9:10 AM
 
Chris, Thanks so much. You are right. The reason my module required vb files when I installed into production was the text 'CodeFile=' was being used in my aspx (markup) files instead of 'CodeBehind='. You are my hero. Look for a few more questions from me soon. I am new to this and have a lot of modules to write. This helps a lot! Paul
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesMy First New Module - Tested OK - But VB Files missing in Production!My First New Module - Tested OK - But VB Files missing in Production!


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