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
Related
I found that the windows visual studio extension is targeted to .net framework and only .net framework (which seems not clearly described in the docs?), after switching our custom mono debugger extension to .net 7.0, with framework not compatible (between vsix project's .net framework 4.8 and debugger project's .net 7.0) error when building the vsix project.
If I switch the debugger project target back to .net framework 4.8 then I can build the extension along with the debugger and create a vsix bundle them togeter successfully.
I tried the previewing visual studio extensibility tools: the out-of-process solution, but the out-of-process way seems not have access to the dte object, thus no way to send the debug adapter launch command. If I use the in-process solution, then we head back to the .net framework target :(
The mono debugger extension is a "3rd party executable file" that launched by visual studio debug adapter. If I manually paste the .net 7.0 version mono debugger to the extension install location, the extension can still work with the debugger. I manage the debugger project and the vsix project within a solution is for easier project management only, in fact they are not referenced directly in code.
I switched our mono debugger project to .net 7.0 is for trying to upgrade our toolset to the newest unified framework (every other tool in our team are upgraded to .net 7.0).
TL;DR, how can we bundle a none .net framework targeted project along with a windows visual studio extension, which is targeted to .net framework only? Or how can we integrate/bundle/add built exe,dlls into the vsix container?
There are some solutions from other stackoverflow answers such as add dlls using vsixmanifest, but it can only add dll file, and the way it handle asset file seems not quite right, it just copy the dll to vsix project folder once, meaning it won't get updated when the dll's project rebuild.
Here I managed to bundle the files in a wonky way:
I create a publish folder under vsix project folder,
then copy the published debugger project file to it, add them as existing file to vsix project, and configure them as vsix content, copy to vsix,
then add a pre-build event for the vsix project, publishing our debugger project and output to this publish folder.
With process above, I can package the published file into vsix when trigger vsix project build.
For anyone have similar issue, you can have a try.
I am planning on using ImGUI for a side-project on visual studio code. I have C++ properly installed such that I can run simple programs on a terminal/command prompt. Thus, I have the correct compiler path for the C/C++ configurations.
I was following this tutorial- https://www.youtube.com/watch?v=VRwhNKoxUtk - until 0:50, where properties was being accessed by clicking on a project. I could not find properties because my C++ and other files are under one file.
I have looked into the documentation from Microsoft Visual Studio Code and several other resources on creating workspace, but that alters my files and the compilation process does not work.
Is there a way of getting the files from https://github.com/ocornut/imgui - with the necessary header and .cpp files- and being able to program in ImGUI without working under a project, but instead a file?
I have tried putting the header files in the include path, but I am not sure if this will work. In that case, why do I need the .cpp files from the github repo? I assume the compiler path does not need to change
The new imports used are as follows
#include <glad/glad.h>
#include <GLFW/glfw3.h>
I am a beginner to visual studio code and C++, so any advice or help would please me.
what is the title of the section at 0:50 of the video:
Importing into Visual Studio
The screen on the video does not look like Visual Studio Code.
VSC does not have a toolbar or a Solution Explorer
I am using VS2015 Enterprise. In which I have created MVC Project and added file named "angular.min.js" downloaded from angularjs.org but Angular intellisense is not working. Although I have referenced this file in my custom javascript file named "AngularScript.js" as shown in figure.
The most easiest way to get intellisense is to install angularjs package from "Manage Nuget Packages" as shown in figure below.
just install this package and this will resolve all your issues regarding intellisense and other. Do this and enjoy the AngularJS intellisense in your application. :-)
I'm a newbie to D3D dev and when i tried to compiled the d3d11 tutorial example given by microsoft it always failed with unresolved external symbol.
I tried to copy the lib folder to project, and add .lib file dependency in project properties but didn't work
While it's not clear from the description, it seems that you are using the Win32 desktop Direct3D tutorial sample and not the Windows Store app sample. I suggest trying with the latest version of this tutorial from MSDN Code Gallery.
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.