I am attempting to build a runtime license for a third party component for ASP.NET. The instructions are to place the "licenses.licx" file in the root folder of the site. The file is also embedded as a resource
However, the option to build the runtime license is not shown when I right click on the file.
There's also some confusion to what it is meant by the "root folder of the site" Is it the root folder of the project?
It turns out that there is one vital step missing. I first have to open my solution as a web page, and move the license.licx to be in the same folder as the solution file.
Only when I open the solution as a web page, can I see files in the root folder inside the solution explorer. There I can right click on the license.licx file and see the option to build run-time license.
Related
I have just downloaded the source package for DNN 8. I created a folder for the site, copied the files there and found the solution named DNN_Platform.sln and opened it with VS 2015. Did a right click and build on the solution and it successfully completed. I navigated to the web site and it gave me the standard install screen to input info such as database name etc. It ran and I was able to go to the web site. It has a single blank page named home with nothing in the page. I can go to some of the admin pages and they are fine. But I got to File Manager and all that I see is the bread crumb telling me my page location. Same occurred trying to look at the Page management screen. When I look at the available modules there are only a few there and there is no module for either the file manager (Digital Assets) or page manager. It feels like I am missing a portion of the build. I Googled to find install instructions for DNN8 but so far can't find any. I found instructions for earlier source code installs but the DNN8 package is a lot different. Can someone tell me where I can find this information or shed some light on what I have done wrong? I also did a standard install for DNN8 and all the modules are there.
In the root of the source directory there are two solution files:
DNN_Core.sln
DNN_Platform.sln
Open both (two different Visual Studio instances). First build DNN_Platform.sln, then build DNN_Core.sln.
Once you've built both you will not see the module directories in Visual Studio unless you click on "Show all Files" in solution explorer. You will also find them using File Explorer.
I'm trying to add a licence.rtf file to my setup project, I've followed this stackoverflow answer step by step in order to add the licence file.
What seems to be happening is when I add the license file it doesn't add it as an embeded resource so when I remove the file from my local machine i get a complie time error...I also do not see any property which let's me change the license file to an embeded resource.
This is the error that I'm getting
Please let me know if anyone has experienced this issue before and how can I go about fixing it
UPDATE:
When you add the licence.rtf file to the Setup Project it does not have a BuildAction property which can be set to EmbededResource.Tried that
I seem to have figured it out. Instead of trying to add the License.rtf file to the setup project I've added it to another project in the solution.
Once done I reference that file in my setup project and when the setup file get's compiled the license file is embeded in the exe.
Click the file in solution explorer, view properties. Then change Build Action to Embedded Resource.
The usual way to show a license agreement in a Visual Studio setup project is as follows:
Go to the User Interface view in the IDE. Right-click "Start" and then Add Dialog, add the License Agreement dialog.
Right click the dialog to move it up or down. Right-click and Properties Windows shows properties where under License you can browse for your custom license RTF file.
I have an issue that is occurring with one specific solution. Everything works fine for the others.
When you right-click on a web project to publish, it asks you to specify information before you publish. I choose File System, tell it to delete all files, and specify a path. After I publish and shut down the solution, I will open it later again to do another publish. After I do this, I have to set everything back up. This means browsing to the folder every time to point to the publish location.
No other projects in any other solutions have this issue. Does anyone know what could be causing this?
The simplest thing to check is that the local storage file where the web publish settings go isn't read-only. For example, make sure you haven't accidentally checked it in to source control.
The publishing profiles file will be in the same location as the project file, named $(ProjectName).Publish.xml.
Another solution I got here. After I found publish.xml file no where, I did following steps and it worked:
Right Click on Project in Solution Explorer.
Select "Build Deployment Package"
You're done.
Hope this helps somebody.
The publishing profiles file will be in the same location as the project file, named $(ProjectName).Publish.xml.
just delete $(ProjectName).Publish.xml file in project folder.
I know I can add a icon to the Resources.resx file of a project and then reference that icon from within the code.
How do I set the icon of the entire EXE from the resources? All I see is a place to browse for another file. I want to use the current icon file that I have in my resources and not have to have a duplicate file in my project...
thanks
The way that the adding of an application icon is that you must select it from the local file system, and then it is embedded into the application at build time. As far as I know it is not possible to have it first pull from a resource file.
One solution I always use to prevent duplicate file references, is to create a solution folder such as "Project Dependencies". And then all refereces are made from that folder, so when building it pulls from the Project Dependencies folder.
This would work for resource files also, just copy them to the solution folder first and then drag them into your resource.
And for the assembly icon, just browse to the Project Dependencies folder as well.
Good Luck!
I have a multi-project solution. I believe it is best practice to put all externally referenced assemblies (e.g. OSS stuff) in a folder that is on the relative path of the solution and it's component projects.
I'd like to create a real folder called Libs within the same Windows folder that contains my .sln file and add it to source control (Team System). I can't seem to figure out how to do this from the Solution Explorer. I can only do this from the Source Control Explorer. There does not appear to be a way to add this Libs Windows folder directly to the solution itself.
I see that you can create a "solution folder" -- but this does not correspond to a real windows folder and it apparently places the files within the top level solution folder.
I was wondering if there was a way to add the Libs folder to the solution so that it was apparent it was there and referenced by the component projects.
Here's my structure in TFS
Development/
Trunk/
Binaries/ -- Shared libraries
Source/
Test/
Docs/ -- Documentation
TeamBuildTypes/ -- Build definitions
You cannot do what you want directly in visual studio with the projects. The best thing you can do is create an external folder, plece the libraries in there, THEN add a solution folder and "Add Existing Item", and then select the libraries and click "Add As Link". It's actually hidden in the dropdown of the "Add" button. Click the little arrow and it will give you the option to "Add as Link".
I've typically seen third-part DLLs placed in a "ThirdParty" folder outside of any specific project in source control. Then in your project reference it from the "ThirdParty" folder and make sure Copy Local property of the reference is set to true.
Take a look at the Streamed Lines paper it suggests a number of structural patterns for dealing with third party dependencies
"Thanks Micah. The Add As Link option I think is new with VS2008. Alas, this is a VS2005 project and I don't see it. "
You can't use "Add as Link" within solution folders anyway.
For what is worth, we have a "PrecompiledLibraries" folder (what Micah called Binaries) outside the solution, and we reference there. If a new external lib changes, we simply place it in, relink, test and recompile. If everything is ok, commit and voila.