I have a simple WinForms app that I'm trying to package with MSIX. The app itself requires additional files that when I build the MSIX App Project doesn't copy/include.
Specifically this LIBVLC folder that gets included during the WinForms app build itself.
If I manually copy that folder over into the AppX build folder, everything works. Obviously I'm trying to automate including that folder.
Folder manually copied over in screenshot below:
How can I accomplish this? GitHub minimal repo:
https://github.com/aherrick/MSIXWinFormsLIBVLC
I suspect that this line is your issue : https://github.com/aherrick/MSIXWinFormsLIBVLC/blob/0e717828a16e796a7a27e415cf45d33a50327da9/MSIXWinFormsLIBVLC.AppPackage/MSIXWinFormsLIBVLC.AppPackage.wapproj#L80
The nuget package isn't really well understood by the build tools as those are native files that we collect "before build". It seems to cause issues when a project references a project that references the nuget package, and the usual workaround is to reference the nuget package directly in the topmost project.
Is it possible to reference a nuget package in a .wapproj ?
If it isn't, that's an issue for this repository https://code.videolan.org/videolan/libvlc-nuget/ . Contributions welcome
This is about WPF project with Dynamic module loading and navigation using prism. I am trying to figure out - how the WPF project loads shell module so that all related files such as Bootstrapper, catalog, etc. are initialized to register the modules (WPF projects) through catalog. This is required so we can use prism module loader.
More details below -
We are migrating a Silverlight project to a WPF project.
Silverlight Solution has following projects
MyProject.Web (aspx) with default.aspx which is initializing shell module ("I believe") by following code
<param name="source" value="ClientBin/ShellModule.xap" />
ShellModule Silverlight project with catalog.xaml which registers all Modularity:ModuleInfo and Bootstrapper.cs inheriting UnityBootstrapper which returns IModuleCatalog
Other Silverlight Module projects
I am trying to figure out how would WPF project achieve it without the MyProject.Web project and without a default.aspx
My very odd random guess - from App.xaml of Root project somehow?
WPF - https://prismlibrary.github.io/docs/wpf/legacy/Modules.html
Silverlight - https://www.wintellect.com/dynamic-module-loading-with-silverlight-navigation-using-prism/
I was reading a DNN manual called 'DotNetNuke Module Developers Guide' for developing new modules from scratch.
The manual says to create a class library project and add reference to DotNetNuke project.
I do not find any such project in Community version source code for version 7.00.04. However, I can see DotNetNuke.Web and DotNetNuke.Web.WebClient projects but none that is called DotNetNuke.
There isn't a DNN project, but there is a DotNetNuke.dll, add a reference to that (the project I believe is DotNetNuke.Library)
I would also suggest taking a look at my Templates for DNN, they make doing module development easy http://christoctemplate.codeplex.com/
I am developing Windows code in C using Visual Studio 2010.
I am working on several related projects: a static library, a DLL, and an executable. The DLL should have the static library linked in, and the executable depends on the DLL. (I am using "implicit" DLL linking; I do not need to control the DLL loading and unloading.)
Right now I have three separate VS2010 projects, but I know it is possible to set things up as "subprojects": the static library should be a subproject of the DLL, and the DLL should be a subproject of the EXE.
I want to solve the following:
When I rebuild the EXE, it should rebuild the DLL if need be, and in turn the DLL build should rebuild the static library if need be. I'd like to just have the EXE open, hit the F7 key, and everything builds.
When I rebuild the EXE as Debug, it should link with the Debug .lib file from the DLL; likewise when I rebuild the EXE as Release, it should link with the Release .lib file from the DLL. If I set up the subprojects correctly, will this Just Work automatically?
EDIT: I have made progress. First, in the DLL project, I used File / Add and then chose Add Existing Project to add the static library. (This is only available on the File menu as far as I can tell! It definitely is not in the right-click menu.) Second, I clicked on the DLL project in the "Solution Explorer" sidebar on the left, then right-clicked and chose Project Dependencies... and set that the DLL project depends on the static library project, which should build first. Visual Studio seems to have then magically set up the link dependency for me, and when I hit the F7 key in the DLL project, it will build the static library project.
I tried repeating the above steps for the EXE project. Now it will build the DLL, but it isn't linking things correctly yet; the linker is complaining that the functions exported from the DLL are not available.
You can't really have 'sub-projects', but you can have multiple projects in a solution. Then you can mark their dependencies on each other by opening the "Project | Project Dependencies..." menu item.
You can also make a 'stronger' dependency between some projects by having one reference another one (from the "Project | References..." menu item). For example, if an application project references a library project, that library will be automatically be linked to the application.
I have it working. Here are the steps I used to make it work:
Choose File / Add / Existing Project... and navigate to the other project that you want as a subproject. Choose the .vcxproj file and okay the dialog. You have just added a project as a subproject.
Right-click on the main project in the "Solution Explorer" sidebar pane on the left, and choose Project Dependencies... Click on the subproject to make it a dependency of the main project, then okay the dialog. This is a tabbed dialog, and the other tab is "Build Order"; if you click on that you can make sure that Visual Studio will build the subproject first and then build the main project. You have now set things up so that the subproject builds first, then the main project.
Right-click on the main project in the "Solution Explorer" sidebar pane on the left, and choose References... In the references dialog, click on the Add New Reference... button. Make the main project reference the sub-project and okay it. You have now set things so that the linker will link the output file of the sub-project.
I performed the above steps to make the DLL project have the static library project as a subproject, and I again performed these steps to make the EXE project have the DLL project as a subproject. But I got build errors about the static library file not being found. So I think that, even though I set the static library as a subproject of the DLL library, it is essential to set up that dependency within the EXE project; the dependencies don't seem to be transitive! I performed the above steps to make it clear that the static library is a subproject of the DLL subproject of the EXE project, and that fixed things.
Now when I hit the F7 key, everything builds. If I choose Build / Clean Solution it cleans all three projects. When it links, it gets the Debug or Release library files as appropriate and links them in.
Sometimes when I hit F7 and build, the build fails, saying that the dependent library is outdated; but if I just hit F7 again then Visual Studio rebuilds the dependent library and the build succeeds. If I hit Ctrl+Alt+F7 to force a clean build, the build succeeds every time. I don't know why Visual Studio has this quirk.
How do I share files between WPF and Silverlight projects in Visual Studio 2010?
You can download Project Linker for Visual Studio 2010 in the Extension Manager. Just search for "Project Linker". It works perfectly!
The project linker download can be found here at the bottom of the page in the "Files in this Download" section:
http://www.microsoft.com/downloads/details.aspx?familyid=fa07e1ce-ca3f-4b9b-a21b-e3fa10d013dd&displaylang=en
And just in case you were also asking about its usage, here is a link to the usage information:
http://msdn.microsoft.com/en-us/library/dd458870.aspx
It doesn't appear to have been released as a self installer for VS2010. However, the code does appear to have been updated to allow the plugin to run in VS2010.
Have a look at this discusson thread. About two thirds of the way down the tread, it gets to the point where they give that link and discuss the steps for making it work. Here is the link to the source code updated for VS2010.
The steps to use the code to generate an installer that will work for you are (ripped from the linked thread):
open solution in vs2010
compile as release
add a new VSIX project (template located under c#>Extensibility).
In the VSIX project you need to add two "content" items
- a "VS Package type" as the output of the project linker project,
- a "Custom Extension" Type - as a file and browse to the compiled project linker helper dll
HTH