I'm learning dx11 and I have been trying to import 3D models into my little game, I have been trying to copy the import method from the DX11 HLSL sample, so I copied the DXUT folder into my project, but for some reason It's giving me an that 'GetVersionEx' is depraciated. I am a begginer programmer, I looked into the problem and apparentl I should be using 'VerifyVersionInfo' I looked at examples but I don't know how to use them to fix it using that.
And I'm wondering why is this error is not coming up when I try to run the Sample.
The first thing to know is that the venerable DirectX SDK has been deprecated, and as you are using VS 2013 or VS 2015 based on the warning you are getting, you already have the Windows 8 SDK which has most of what you need to get started. See MSDN for more information, and take a look at this post and this post.
The warning you are getting from VS 2013/2015 about GetVersionEx is an unrelated but important issue. The fact that you are seeing it when building DXUT from the legacy DirectX SDK is because that code hasn't been updated since VS 2010 was shipped. See MSDN and this post.
You have a number of options for getting utility code for Direct3D 11.
The latest version of DXUT can be found at GitHub. This version does not require the legacy DirectX SDK to build and works with VS 2013 and VS 2015. For more on why you might or might not want to use DXUT can be found here.
Similarly the latest version of Effects for Direct3D 11 is on GitHub, and again works on VS 2013 / 2015. More information and a number of important disclaimers can be found here.
If you are starting fresh, I recommend you avoid using DXUT or FX11, and instead focus on using the DirectX Tool Kit. See the tutorials for it including the Rendering a model lesson.
For model and texture processing, you should see the DirectXMesh, DirectXTex, and Content Exporter projects.
Related
I have a very odd problem where I will apply a recommended change that uses a C# 8.0 language feature (in this example I'll use compound assignment). I then get a red squiggly with the following message...
C# 8.0 language feature
This is a net5.0 project I have tried setting my language version property to any of the following...
<LangVersion>9</LangVersion>
<LangVersion>9.0</LangVersion>
<LangVersion>latest</LangVersion>
All of them show the same behaviour. The only way I can get the error to go away is by setting the property to 8 or 8.0 which seems a somewhat retrograde step!
I'm using Visual Studio 2019 and I'm fully patched and up to date as of the time of writing, along with the latest version of ReSharper.
The code will compile without problems but the squiggles are generating noise. Has anyone else found this and has any ideas how to make it go away?
This looks like it was a ReSharper issue - JetBrains have introduced a new tool called Jetbrains Toolbox that seems to manage their updates now. My installed package was telling me it was up to date when it wasn't - I looked deeper and I was running ReSharper 2019.1 and not 2021.1
I have been doing some programming in VB.NET on Visual Studio Express 2015 for Desktop. I recently started looking into F# and like the functional paradigm. As a result I have been trying to find a way to use VSE2015 as my IDE for F#. However, I have hit some problems. First of all, it has been difficult to find out if it is officially supported. The .NET blog suggests that it is (at least version 3.1.1, and the announcement for 4.0 RTM does not mention otherwise), but when I try to install F# Tools (4.0) it seems to choke on some components called VWD and WD(?). 3.1.1 seems to install OK, but then I still can't open any F# projects (fsproj). When I try to install FSharpVSPowerTools, it tells me that my platform is not supported.
Am I trying to do something that is not possible? Have I missed some steps? Any pointers would be appreciated. Thanks.
(Incidentally, I can't use the Community edition because of the licensing restrictions)
Edit: I have tried VS Code, but it works differently from VSE, and I would have to do a whole more learning. In addition, I want to use the VS template for creating XLL's. Edit 2: it has been pointed out that you can reference excel-dna in VS Code, but setting it up is not as straightforward as in VSE2015 (at least for VB.NET and C#.NET.
I want to port a Compact Framework/Windows CE app to Xamarin to create Android and IOS (and possibly Windows Phone) "versions." I reckon I need Windows 8 for Windows Phone (8) but for now I thought I could get started with Android and IOS in moving this prehistoric app into the 21st century.
According to this article, I first need "Project linker" and can NuGet it, but searching for it via Tools > Extensions and Updates in VS 2013 returns no search results.
That article says you need VS 2012 or better; the direct link to "Project Linker," though, says it supports VS 2010.
Where do I go from here?
UPDATE
I went here, and am in the processing of downloading.
UPDATE 2
Here, it says, "Modern Integrated Development Environment (IDE) – Xamarin uses Xamarin Studio on Mac OS X, and also Xamarin Studio or Visual Studio 2010 on Windows."
Yet in VS 2013, I do have project types now for Android and IOS*, so I reckon that's just a typo (hasn't been updated)?
although I don't have a Mac, so that is not possible for me right now; also, since I'm still on Windows 7 at work, Windows 8 Phone apps are not yet a possibility, either. So at present, Xamarin within Visual Studio is simply a replacement for Eclipse/Java in the creation of Android apps.
UPDATE 3
I've been waiting for something better than PhoneGap, and I think maybe I've found it. If MS were to buy this company and bake Xamarin into Visual Studio -- voila!/yowza/wow! The cats in Cupertino will have to reach for the Pepto-Bismol!
That's a bit outdated and there's a much better approach available today.
You can use Portable Class Libraries (PCL) to share code across project spanning iOS, Android, Windows (Phones) and even OSX.
See this article (and where it leads) for more details.
I certainly agree with #poupou that PCL's are the way to go (if possible). I would recommend James Montemagno's app on github. He just created this for channel9 using VS 2013. I just created a cross-platform app based off of this and it worked out well. I would only use the file-linking for the platform specific implementations with compiler directives. This can be seen in his ServiceRegistrar class in said app.
This SO answer actually explains how to get the 2012 Project Linker to work with 2013 if you still want to go that route and gives a link to the extension.
Also, you may want to check out MvvmCross. It is open-source, has a large user-base and following, and really helps with maximum code re-use. Best part, it uses PCLs and all of it's features (plugins) are available via nuget.
I would recommend reading the article #poupou posted, watching James' channel9 videos on his github page, and (if you want to check out mvvmcross) watch #slodge's N+1 videos on mvvmcross.
I am a beginning programmer university student and I want to apply myself outside of class with a side project. I wanted to start programming some simple directX stuff in C++ for practice and preparation for future classes.
However, I have Visual Studios 2013 installed and the DirectX SDK June version installed, and I can't seem to find any directX templates in visual studios. In tutorials I have watched, when a person goes into visual studios 2013 and clicks on "Visual C++", they have a lot more templates show up, including DirectX ones.
What step am I missing to be able to see these things in my Visual Studios 2013 professional?
Thank you in advance for the help!
There is no built-in templates for desktop DirectX, since you have installed the DirectX SDK, I recommend you use the Samples/Demos from the SDK(you can find it from DirectX Sample Browser), there is a sample called Empty Project, you can install that sample and write your code based on it.
There are only templates for DirectX Windows Store Apps. I cannot remember if it ever was DirectX Desktop templates in Visual Studio.
On a picture here you can see two default DirectX Windows Store Apps templates and new templates which you can to download.
Probably, in your tutorial there are some home made templates, or those which can be fond on a web. You can easily make your own template too.
If you really want to learn program for Desktop (and as you are trying to use DirectX SDK it is probably what you want), just follow the code that you can find in books and tutorials. Also it is a good idea not to copy any code, but to start your own projects(s) which will develop as long as you will develop your knowledge.
Note, that DirectX SDK was deprecated a while ago (latest version is dating June 2010). You must use Windows SDK for any new code. Though, you can compile old samples (which requires stuff not present in new SDK) with DirectX SDK. You could find interesting some of Q&A on that topic:
DirectX SDK vs Windows SDK: which one to use?
Working with Direct X and VS2012
and this blog on MSDN by Chuck Walbourn - MSFT :
Where is the DirectX SDK?
Where is the DirectX SDK (2013 Edition)?
Living without D3DX
Happy coding! ;)
I'm working on deciding between Managed DirectX (through MS API Codepack), SlimDX library (managed wrapper for DirectX), XNA (managed wrapper++ for Directx9 only), or unmanaged Directx (20%+ extra development time).
So, the MS API Codepack interests me, because it has support for DirectX. However, I get a feeling that they might not support future versions with the Codepack. My thinking is that they just wanted something to support the version of DirectX that ships with Windows 7.
Is MSI API Code Pack DirectX functionality going to be updated as DirectX progresses?
Thanks
There is no way to know this.
However, I will say, I've been using SlimDX for a while now, and it's very, very well thought out. The advantage there vs. the other options I've tried, include:
Support for DirectX 9, 9Ex, 10, and 11
Clean API - Very easy to port from DirectX samples, but still feels more like .NET
32 and 64 bit native versions
Kept very up to date with DX SDK releases (usually within a couple of weeks of a new SDK, there's a new SlimDX version)
The Windows API code pack has a nice wrapper included, but is problematic for me since it's DX10+ only, so no XP support.