I'm converting a DirectX project to a WinRT project in Visual Studio 2012 and having trouble setting up references to the Direct X libraries. I'm using at a generated Direct3D solution as a guide. I've added what I think are the correct include folders and libs in the project settings but I must be missing something else. In the generated Direct3D solution, the "External Dependencies" tree in the Solution Explorer has a whole bunch of directx headers in there, but I have no idea how that is set up. Simply dragging and dropping DirectX headers doesn't work, which didn't really surprise me.
What could I be missing?
Looking at the problem again with a fresh head, I noticed that the generated DirectX example was using a precompiled header while the project I'm working with wasn't. The precompiled header was including DirectX headers that my project wasn't.
So I added
#include <DirectXmath.h>
#include <d3d11_1.h>
and it compiled.
Related
I'm trying to add platform-specific code for iOS to my .NET MAUI app.
I'm targeting an iPhone with net6.0-ios:
However, Visual Studio thinks I'm targeting Android:
Compiling and running the app works fine (breakpoints within iOS preprocessor directive are hit), but it's a hassle to have to implement the iOS-specific code outside of the conditional preprocessor directives (with a bunch of warnings saying types aren't available) to be able to get some IntelliSense.
I'm suspecting this is a bug, but curious if there's any workaround?
Edit: Not a bug, I was just being an idiot not realizing the code editor and debugging target don't necessarily have to be one and the same.
Look in the first picture you posted, at upper left corner. ...App (net6.0-android). That is current value of a dropdown, that determines which project Intellisense uses. Change that to iOS.
I cannot find any documentation, if VSTO AddIns are supported by SDK-style projects.
I already installed and used h. van brakels project2015to2017.migrate2019.tool. The resulting project files are usual class libraries and no more Powerpoint AddIns. Thus for example the projects cannot be startet anymore from the IDE for debugging.
The BootStrapperpackage and the ProjectExtension have not been transfered to the new file format. Additionally ProjectTypeGuids were not transfered. Maybe this marked the project as a VSTO Addin in the old style project files.
I'm frustrated I cannot find any statement if the SDK-style project files does support (and in this case how?) or does not support (and in this case why?) vsto addin projects! And furthermore, why does nobody dare to state/write that. It would make things clear and I don't have to waste my time searching for it ...
Thanks for your help,
Karl
To my knowledge, a VSTO project file cannot be converted to the newer SDK format. This is mostly because of the ProjectTypeGuids.
In order to properly convert a project file to the newer SDK format, there should be an SDK for the ProjectTypeGuids.
To my knowledge there is no VSTO SDK to use in the header of your project file.
[Edit]
MSBuild 15.0 introduced the concept of the "project SDK", which simplifies using software development kits that require properties and targets to be imported.
The information from the above link indicates that Project SDKs are the preferred successor to the "standard" MSBuild props and targets.
[Edit 2]
Have you considered the newer web based Add-In?
I've been through a lot of similar issues, but could not find anything that worked for me.
I'm upgrading my IDE from the VisualStudio for Web (v10) to Visual Studio 2015 (v14, I guess) Community Edition.
The main project that I'm trying to use on the new IDE is a MVC 5 (5.2.3), with EF 6.1 (6.1.3) and a bunch of other stuff.
Problem is: When opening the project on the new IDE, everything looks fine (it even compiles and work). I got the MVC context menu working on the project explorer (showing the "Add Controller..." and "Add View..." when appropriate). Only (really annoying) thing is the Razor Intellisense.
When I do open a View file (.cshtml) I receive warnings on several helpers, some of the "using" are greyed out (even though they're supposed to be needed) and the #model myModel is shown like everything after the #model directive is not razor (it's treated like HTML by the intellisense coloring).
What I've already found and tried:
I've already tried to clear the UserData from the vs (devenv /ResetUserData)
I've already tried to run the VS2015 in safe mode
I've already tried to run VS2015 as Administrator
I've already tried to set the Project's target framework to 4.5.1 (used to be 4.5)
I've already tried to open the project on Visual Studio Community 2013 saving it there before trying to use it on VS2015.
When creating another MVC project from the VS2015, everything works fine.
Here's an example of the annoying issue:
Ok, finally got it.
Posting what I found out believing it may help someone else:
What seems to cause the problem mentioned is the fact that the project was created on an old MVC version (with older Razor, EF, etc).
As stated in this answer: Visual Studio 2015 Razor View MVC Types not recognized, VS2015 tools may not work for older MVCs.
The solution is to update all your packages to [at least] the minor versions accepted on newer MVC (5?). To do so you can use the list in this website: http://www.asp.net/mvc/overview/releases/how-to-upgrade-an-aspnet-mvc-4-and-web-api-project-to-aspnet-mvc-5-and-web-api-2.
Once everything is up-to-date, open the web.config files located on root of your application and on the Views folder. In there, you will probably find some references to the older versions of MVC and Razor. Update those versions values (all of them) to match the updated versions of your packages (you may create a new empty MVC project on the new Visual Studio and check for those values as a hint of what they should be).
This step is the catch! Since, even if you update you project's packages, some web.config references may still mention the original versions.
Clean the solution (Build > Clean Solution) and close the project. Reopen and compile it. Now [hopefully] everything should be working fine.
[Edit]
One more thing: If your project was also updated from Framework 4.5 to 4.5.1 during this IDE transition, you should also install a NuGet package called "Microsoft.CodeDom.Providers.DotNetCompilerPlatform" (as stated in https://support.microsoft.com/en-us/kb/3025133).
I want to build this project on windows from source code.
http://sourceforge.net/projects/portableapps/
I have downloaded the source code. But I have no idea how to build it.
EDIT---------
Actually I downloaded the source codes. But, I don't know using which software I have to open/build the source.
For example, for .NET projects, I would use Visual Studio. I need to know which IDE is required for this project
If you mean the launcher, then the source can be found here. I was able to build 2.0 beta 5 from source. I got an error running it, but didn't investigate further.
I have to say, the source code for this project is pretty well hidden. A comment in this blog post suggests that the latest version requires Delphi XE. If you are using an earlier version, this could be the problem. Otherwise, you'll need to be more specific about what's going wrong.
Using the latest stable of CC.NET (new to it) and VS 2010.
I have defined project files for simple C# projects (4 in total) and one MVC Project.
The C# projects all compile correctly; however, the MVC3 project refuses to build.
I receive the following error in CC.NET:
error MSB4019: The imported project
"C:\Program
Files\MSBuild\Microsoft\VisualStudio\v10.0\WebApplications\Microsoft.WebApplication.targets"
was not found. Confirm that the path
in the declaration is
correct, and that the file exists on
disk.
After searching around and finding This link
and This other link (both referring to older versions of Visual Studio), it seemed that the general solution was to copy these files from that directory to the solution directory, add them to the solution with visual studio, and then change this line in the .csproj file:
<Import Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v10.0\WebApplications\Microsoft.WebApplication.targets" />
To this:
<Import Project="$(SolutionDir)\Microsoft.WebApplication.targets" />
However, this technique that worked for other VS Versions produces a different result in VS 2010: I receive the .NET Project upgrade wizard, as if upgrading the project from an old version of .NET. This strangeness is compounded by the fact that even if I do an undo and re-save the file exactly as it was, I receive the same message. It's as if the project has been marked dirty or something else has changed somehow.
Anyone have any ideas? This seems like it should be easier, but I can't seem to find another resource on it anywhere. Hoping StackOverflow will come through per usual. :)
Thanks in advance for any help!
The .targets file for v10.0 also has an assembly in the install folder - Microsoft.WebApplication.Build.Tasks.dll. Did you copy that file over as well? That will likely be necessary for the .targets file to work correctly, though that may not be the cause of your problem.
It sounds like CC.Net isn't getting a proper reference to the msbuild executables.
Trying installing both of these on your build server (that's who I was able to get past that exact error).
Links :
Windows SDK .Net 4
VS2010 Integrated Shell