I download task manager from this site, after the module has been downloaded I load installtion zip file as module to the DNN.
How can I create solution in visual studio from this module(task manager solution)?
I would start by following the tutorial/directions linked on that codeplex page
http://www.dnnsoftware.com/wiki/page/module-development#_Beginning_Module_Development_Video_Series__6
You can also install the SOURCE version of the module http://dnntaskmanager.codeplex.com/releases/view/73062
then you will have the VS files you need. One thing you will need to do is recreate the .DNN file though as DNN makes that go away (you can copy it from the ZIP file)
Related
I recently started having an issue with an Windows Forms application that uses ClickOnce to deploy, in that, when the install completes, it is missing a data folder that contains a zip file and some *.xlxs files needed for the application to run.
This application has been deployed using ClickOnce over numerous updates for the past few years without any real problems. This issue just started happening around the end of December 2017.
I am using VS2017 for the builds. I am using .Net Framework 4.5.2 and I am developing on Windows 10 Enterprise, v1709, build 16299.192
When I publish the application, whether to a local folder on my Dev computer or to the Web Server we use for customer access to download the application; when I look at the published files an I view the Application Files folder, in the folder for the latest version, I can see the Data folder and it has the files as expected.
However, when we run the installer, it doesn't copy that Data folder to the C:\Users{username}\AppData\Local\Apps\2.0\Data\MXTKKEP7.G7K\8W0HCWQ1.AT0\conf..tion_97fe94acfe5f3262_0002.0001_27630dc69b57826e\Data\ location.
When I then run the application, I get this error;
If I manually copy the Data folder to that location, the program runs as expected, without the error.
I get the same problem, whether I click on the *.application file or right-click on the setup.exe file and select "Run as Administrator".
Is this some kind of new security issue because the Data folder has *.zip and *.xlsx files in it?
Has anyone else ran into this kind of problem?
Check include state for you zip and xls files. Goto Publishing project property > Publish > Application Files > And set for you files in publish status column.
If they are missing please check this article:
[To add files to the Application Files Dialog Box]
https://learn.microsoft.com/en-us/visualstudio/deployment/how-to-specify-which-files-are-published-by-clickonce
I would like to be able to publish from visual studio. I am able to do this
I have different configurations for Debug,QA,Release. I am using config transforms and they work fine.
ISSUE: when I publish the I want the Debug, QA,Release to be published to their respective folder example E:\Application\Debug and so on. I am able to do this by changing the Publishing folder location and Installation folder location manually. How can this be such: f I change the configuration these locations are selected automatically. So when I need to publish a particular version -> and all I need to do is
change the config
press the publish now button.
Thanks!
The only possibility I know of would be to use a Build Server and build if the Source code changes (probably seperate branches) and have build definitions for each case.
This would mean that you would have to have a kind of source control (Git, Mercurial, TFS) for the Project and the resources to run that kind of service or use a Service on the internet.
Build Server for local installation:
TeamCity
Team Foundation Server
Build Server via Internet:
VisualStudio.com
(Those are the onse that come to my mind because I have used them before. There are much more available)
With a 2012 SSDT database project and a Integration Services project within it using project deployment model, after a build, a .ispac file is not created for me. Is there a setting or option that is necessary to allow this to be created?
The project builds successfully, and successfully creates the .dacpac file too. Building from the solution or individual project, the .dacpac file is created, and I see both projects are built successfully when built from the solution. I can also successfully create a .SSISDeploymentManifest file too. Of course, the run the all the packages without error as well.
Also, the Non-Default Properties Report shows only MaxConcurrentExecutables and EnableConfigurations for project level properties have non default values.
I feel like there is something small I'm missing. Any help is appreciated.
If a package is converted to use the package deployment model, a .ispac is not created when the project is built. It is only created when the project is using the project deployment model. The answer was in the question the entire time...
I have a WPF application.. I need to create 3 setups, each setup is for an environment(development, staging and production), I've put each environment configuration into App.config file of my main UI project. I need Installshield to pull the appropriate configuration file while creating the setup file.
A question: Is there a way to do it differently?
thanks,
There are several approaches you could take. Here's one:
In recent versions of InstallShield (Professional and higher editions), you can override Path Variables on a per-Release basis. If you craft your source filesystem and source path correctly, this should let you select from multiple source app.config files just by building a different release.
I am new in dotnetNuke. I am trying to install DotNetNuke_Community_05.06.02_Source.zip file.Firstle i extract it to C:\DotNetNuke. There is a release.config file created in C:\DotNetNuke\WebSite\ . Renamed it as we.config. There is another we.config file in C:\DotNetNuke\DotNetNuke_Community_05.06.02_Source\Modules\RazorHost\ renamed it to web1.config. I configured it in IIS6.0 .Created a Database in SQLServer2005 named -DotNetNuke.Changed the connection string as directed by the installation guide. When i am trying to open the installtion wizard through browser it shows an error
Server Error in '/' Application.
Configuration Error
Description: An error occurred during
the processing of a configuration file
required to service this request.
Please review the specific error
details below and modify your
configuration file appropriately.
Parser Error Message: It is an error
to use a section registered as
allowDefinition='MachineToApplication'
beyond application level. This error
can be caused by a virtual directory
not being configured as an application
in IIS.
Source Error:
Line 56: Line 57:
Line 58:
validationKey="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902"
Line 60:
decryptionKey="F9D1A2D3E1D3E2F7B3D9F90FF3965ABDAC304902F8D923AC"
In order to use the source package you must compile the code in release mode before attempting to access the website.
Being new to DNN, I recommend starting with the install package which will not need compiled, or even easier, you can get DNN through the Microsoft Web Platform Installer. WPI will also take care of all the dependnacies that may need configured on your computer.
I'ld like to clarify the intention behind downloading the Source Package. Were you intending to start developing and changing the dotnetnuke framework to suit your needs or did you want to set up a website that you could build modules against on IIS?
If you're intending to develop modules, I'ld suggest downloading the Install Package, creating an IIS site under Default Web Site.
- There's no need to change connection strings if you're using the database file that's in the App_Data folder.
- All you need to do is set the Folder Permissions for Network Service or IIS_IUSRS based on what application pool you're running.
- The url to the site will be http://localhost/xxx.
There are 2 ways to build modules in DNN. The Website Project and the Web Application are two different ways. They produce source code and dll's respectively. If it's internal, any way's good. If it's external facing, you might want a little bit more speed, so go Web Application.
However, If you're intending to muck around with the DNN Core Framework and adjust things, the Source is the way to go. there's no need to adjust the settings, just open the website project up in Visual Studio and away you go.