I want create a module with DNNModule template but when create module template get this error.
The Web Application Project DNNModule7 is configured to use IIS. The
Web server 'http://dnndev.me/desktopmodules/DNNModule7' could not be
found
I search in internet and found a solution I run as administrator visual studio but in this way the DNNModule template option hide .
Please advice
Follow below steps to kicked off this error message:
Open IIS.
Create new website dnndev.me on IIS Server.
Folder of this website must be the path of your actual DNN website from where you are creating DNN modules.
Try to create modules using Chritoc's DNN template.
For more information about this error, check this URL.
Please let me know if you have any questions.
Related
I have searched all over the web, read and tried every solution I could find and none of them have solved my issue.
I have a web site on Azure. It is an App Service.
I am developing with the latest patched Visual Studio 2015.
I am able to right click in server explorer on my web app and attach to debugger.
None of the break points activate. They all have the error that symbols have not been loaded.
I made sure to build the site in debug.
I verified that the PDB files are on the server (using service explorer and looking at actual files).
I verified that the PDB files match what I have by date and time.
I tried to manually attach the debugger using the menu.
I put in mysite.azurewebsites.net:4020 as the server and am asked to log in. I use my credentials and they don't work.
I tried created a username and password on the azure portal credentials page for FTP. I tried using those and it still won't let me log in.
I am able to deploy using Web Deploy in the publish wizard.
I have no idea how to fix this. I must be able to debug my site.
I have 2 slots and tried debugging either of those and that doesn't work.
I tried debugging the main (production slot) and get the same results.
Help???
I have created a DotnetNuke Project. It is working fine if I import .zip file of it as a Module in DotnetNuke.
But if I run the project in any browser, it keep throws following error. I am trying to get rid since few days but still not get any solution. :(
Unable to start debugging on the web server. The web server is not
configured correctly. See help for common configuration erros. Running
the web page ourside of the debugger may provide further information.
I have configure Start http://dnndev.me/ and Project Url to http://dnndev.me/desktopmodules/MyTest2
Can anybody please suggest me.
After set Debugger = True in web.config file of dnndev.me
First thing to do is open the WEB.CONFIG file in the root of the DNN website and make sure that debug is set to true.
So I'm building an MVC6 app in Visual Studio 2015 and have managed to figure most stuff out, however, I haven't yet worked out deployment.
In MVC4 (what I was using before), our process* was publish to a folder, then setup the website in IIS (Right-Click on Sites -> Add Website).
Actually, our process is set it up in IIS and TeamCity, but not for test apps like this :).
I followed this process and obviously it's trivial to setup the IIS website and publish to the correct folder...but that does not actually work for me.
We're running IIS 8 on Windows Server 2012 and we've installed the .Net 4.6 runtime on the server.
The following steps have worked for me and should help you host your project on IIS.
Using Visual Studio 2015 Preview as your IDE,
Create an ASP .NET 5 Starter App.
Check that it is working outside of IIS.
Once complete, publish the application. In this example, I have selected the location C:\PublishWebApp.
3.1. When publishing your application, make sure that you have:
Disabled precompilation
Selected amd64
(See image below)
Upon a successful publish, go to C:\PublishWebApp.You should see the folders approot and wwwroot inside.
Now open the IIS Manager (I am assuming you have the ASP .NET 4.5 feature enabled)
Create a new website.
6.1 : Select the wwwrooot folder as the website's physical path. In this example, it is C:\PublishWebApp\wwwroot.
Check the website to see that it is working. If you encounter any errors, please post them here.
If the precompile option is ticked in the Publish Web Settings window pictured above, then you must
Go to the wwwroot folder of your published web application. In this example, it is C:\PublishWebApp\wwwroot.
Locate web.config.
Inside the folder of your published application, there is an packages folder inside of the approot folder which should contain a folder named after your application, with a folder for the version underneath. Inside that folder should be a folder named root. In web.config, set the value for the key kre-app-base to the root folder. For reference, see the line of code below. In this example, the application name is WebApplication10.
<add key="kre-app-base" value="..\approot\packages\WebApplication10\1.0.0\root" />
I Spent hours on debugging the issue finally got it worked, steps:
1) Publish your MVC6 application using visual studio into file system, make sure you are selecting correct DNX Target version in my case its dnx-clr-win-x64.1.0.0-rc1-update1.
In the output folder map "wwwroot" folder to your applicaiton in IIS (DO NOT Map it to sup-applicaiton, only ROOT application in IIS works with DNX for example "Default Web Site").
I have just spent a day trying to get this working. i found this here (search for posts by GuardRex) invaluable, complete the steps the accepted answer gave, that's the start of it.
Pretty much if you try to add an application to a site there is bunch of workarounds and extra configuration needed that is detailed in the link.
For starters:
1)Make sure you have the HttpPlatform handler installed here
2)Seems obvious but make sure .net5 is installed on your server here
I know this is if you are adding an application to a site, but there's some pitfalls and much needed refinements needed for the deployment process at the moment that everyone should be aware of.
When following a tutorial for setting up a development environment for DotNetNuke modules, creating a new project from the project templates caused the following error:
The Web Application Project xxx is configured to use IIS.
The Web server "http://dnndev/desktopmodules/xxx/' could not be found."
How can this be fixed, as the tutorial was followed exactly?
I found two common answers online, which did not work for me but did work for others. I then discovered that I just needed to tweak one of these answers:
Make sure that you are running Visual Studio as administrator.
Make sure that you have set up a binding for your site in IIS for dnndev.me
The KEY part of #2 above, for me, is that when binding was set to dnndev.me I could open the module project in Visual Studio, but not the overall DNN installation in a browser. When the binding was set to www.dnndev.me I could open the overall DNN installation in a browser, but not the module project in VS...
The answer that worked for me in the end was to have two bindings, both set to port 80, one with the Host Name set to www.dnndev.me and the other set to dnndev.me
As it took so long to find this answer I wanted to make sure it was here for people to find easily.
How to deploy an Application page of Sharepoint 2010 to another production server.
I've created an Application page of Sharepoint 2010 inside the mapped layout folder. Everything works nicely now in Visual Studio 2010.
I can debug it after pressing F5, I can retract it and deploy it with Visual Studio 2010.
But when it comes to deploying it to another production server, I have tons of questions.
Basically I don't know how to deploy it to another production server. My first thought was just copy the pages to the Layout folder of IIS and register the referenced dlls. But after I studied a little bit of deployment, I feel my thought is ugly.
I tried "right clicking" on the project name and "package". The Visual Studio generates a "MyProjectName.wsp" in the bin folder. I used the central administration to upload this wsp file. But when I activate it, it raised an error saying "This solution contains invalid markup or elements that cannot be deployed as part of a sandboxed solution. Solution manifest for solution 'af2f9404-3b39-4f90-87f5-31e14b2f9a9a' failed validation, file manifest.xml, line 6, character 4: The element 'Solution' in namespace 'http://schemas.microsoft.com/sharepoint/' has invalid child element 'TemplateFiles' in namespace 'http://schemas.microsoft.com/sharepoint/'. List of possible elements expected: 'FeatureManifests, ActivationDependencies' in namespace 'http://schemas.microsoft.com/sharepoint/'." It seems that my application is not a sandbox, but I can't change it to a sandbox. Because when I do change it, the Visual Studio tells me "The deployment type "TemplateFile" of file "ApplicationPage1.aspx" in Project Item "Layouts" is not compatible with a Package in a Sandboxed Solution.
The Project Item "Layouts" cannot be deployed through a Package in a Sandboxed Solution.
Package validation failed."
Besides, even if I can successfully activate the .wsp file, I am not sure if the application page can be added to the Layout folder. Because I don't know how the .wsp file locate and find my application page? It doesn't have the page in it. Can anyone explain a bit on it?
Thanks for your answers.
1) It's strongly recommended that you use powershell to run your test and production deployments: http://dotnet.sys-con.com/node/1208275
2) Try changing your SharePoint solution to a farm solution and repackaging your wsp.
3) By right clicking on your project in visual studio and adding the mapped Layouts folder the solution packaging handles placing any application pages/user controls that you have in the appropriate directory inside your wsp.