Forum


HomeHomePremiumPremiumDevelopmentDevelopmenterror on creating new solution using DNN C# MVP error on creating new solution using DNN C# MVP
Previous
 
Next
New Post
3/13/2015 12:56 PM
 

working on migrating aspx programs to ascx using the 'Enterprise DNN C# MVP Compile Visual C#'

I want to build a extension P7747469 that will have two modules within it P7747469Wizard & P7747469XSD

1. I can create new project P7747469 OK

2.  during new project 'P7747469Wizard' A problem was encountered creating the sub project 'Test'. The solution already contains an item named 'Test'.
The solution file
'D:\Development\DevDNNMvpVirginP7747469\DesktopModules\P7747469\P7747469.slnP7747469Wizard.sln' was not written successfully.  Check that the location is available, the files writeable and there is enough room on the disk.
A dir
D:\Development\DevDNNMvpVirginP7747469\DesktopModules\P7747469Wizard\Module
was created but no sln

Any suggestion would be appreciated

Lee

 

 

I am disappoint the $80 video is NOT ON DNN C# MVP template 1 - How Setup the Environment to Start Building Modules - Part1/3

 
New Post
3/13/2015 6:19 PM
 

Lee,

I'm not sure I understand which template you are using.  My MVP Template is here: Enterprise DNN C# MVP Module Template for Visual Studio

To learn how to use the template, here is the training video.  This is not a DNNHero.com video.  Toward the end of the video you will see instructions on how to fix common issues.

Once you finish watching that video, then watch my DNNHero.com series to learn more about MVP development and Unit Testing using the template. 

Let me know if you still have issues.

 
New Post
3/14/2015 7:58 AM
 

Scott

Thanks for the reply.

I am using your VSIX DNN C# MVP template.

The video are great for creating new module, but I am attempting to migrate a working stand alone program to a DNN module.  I have found aspx to asc conversion.  Most .cs come across. Any suggestion on tutorial of migrating a menu that links to another program, that have several others with continue?

Will you be updating the VSIX to fix the warning?  Message listed below

Warning

1

'DotNetNuke.Entities.Modules.ModuleController.GetTabModuleSettings(int)' is obsolete: 'Deprecated in DNN 7.3.  Please use the TabModuleSettings property of the ModuleInfo object'

D:\Development\DevDNNMvpVirginP7747469\DesktopModules\P7747469Wizard\Components\SettingsRepository.cs

45

34

P7747469Wizard


Is the first line in View.ascx typical to have .Views.View ?

<%@ Control Language="C#" AutoEventWireup="true" CodeBehind="View.ascx.cs" Inherits="MYeMarketPlacesCom.Module.P7747469Wizard.Views.View" %>

Lee


 
New Post
3/18/2015 5:27 AM
 

Lee,

When I work on the next version of the template, I will address the compiler warning you mentioned.  Thanks.

Also, your question about the "...Views.View".  That is the fully qualified namespace and type name.  Since I organize the Views into a folder called "Views" I add that to the root namespace.  And since the default module view is called "View", that is the type name.  You certainly don't have to name the ascx or type "View", you can make it whatever you want.

If you haven't done so, check out the Module Settings & Views tutorial to get a basic understanding on navigation between module views.  That will give you the best understanding of how to convert aspx pages and navigation into module view navigation.

 
Previous
 
Next
HomeHomePremiumPremiumDevelopmentDevelopmenterror on creating new solution using DNN C# MVP error on creating new solution using DNN C# MVP



Try FREE
30 days money back guaranteed