I'm just starting to learn SFML with Visual Studio. I am faced with problems that my image doesn't loaded with texture.loadFromFile("path"). I found that someone solved this by changing every sfml-~~.lib in linker-input-additional dependency, to sfml-~~-d.lib. So I changed it and solved it! Now I'm wondering what makes the difference: What's "-d"?
-d is the debug library.
As stated on their installation tutorial:
It is important to link to the libraries that match the configuration: "sfml-xxx-d.lib" for Debug, and "sfml-xxx.lib" for Release. A bad mix may result in crashes.
SFML and Visual Studio
Related
I have a problem with VS 2019 editor for a while, but it became a real problem lately.
Specifically, with the editor open, I cannot navigate to objects / classes and their methods or properties
You can see example in the screencast below.
https://www.screencast.com/t/0ceZ4C3TabY
I have the latest version, 16.10.2
This happens on two different PC's.
The problem started in a previous update, but I don't know which. I noticed it few times ago, but I didn't paid attention.
Does anyone else encountered it, and knows any solution?
Thank you
The problem was finally fixed in 16.10.3
I'm new to Xamarin/Android, and so far it's been a pretty frustrating experience, compounded by code/AXML changes seemingly not being built or deployed to the emulator. I often find that a change I've just made seems to get ignored when I build and run the app.
My suspicions were confirmed when it started throwing an exception on a line in MainActivity.cs that I had commented out. Cleaning and rebuilding didn't help, and in the end deleted the bin and obj folders and uninstalled the app off the emulator for good measure (not sure which of these fixed it though).
Is it just me or is this a common issue? Is there anything I can do to prevent it from happening? I'm using VS2015 Community by the way.
Go to 'Tools/Configuration Manager' and make sure that both 'Build' and 'Deploy' options are checked for 'YourApp.Android' for active solution configuration and active solution platform. Then do 'Clean solution' and 'Rebuild solution', it should always work.
It looks like this is a common issue, as yet unresolved.
One of the comments in the above thread suggested that the problem can occur if you've only changed C# code, and unless you also "touch" one of the xml or axml files then the latest version won't be deployed. This seemed to do the trick in my case but it could have been a coincidence - Xamarin seems to be a temperamental beast, and will randomly fail to build or deploy on occasion, perhaps depending on the wind direction, or colour of my underwear that day.
I'm still in the early stages of learning Xamarin/Android, but if I don't enjoy the experience then I'll be jumping ship to Android Studio (although I'd prefer to stick with C# if I can).
I've been working on an MVC 5 code first project for a few months and (seemingly) out of nowhere, Visual Studio is refusing to debug and giving me some strange errors.
When I try to run the application Ctrl+F5 it builds ok but the browser never gets beyond the loading stage, I still have the pinwheel in the browser tab, but the app never loads.
When I try to debug the applicaiton F5 it builds ok, but then comes up with 2 errors, firstly Debugging information for iisexpress.exe cannot be found or does not match. Cannot find or open the PDB file. and then Process with an Id of xxxx is not running.
I've tried loading symbols from MS (https://stackoverflow.com/a/8138518/1778169), using a different database name, uninstalling VS extensions, performing all Windows Updates, repairing the VS installation and even reinstalling VS entirely. Nothing seems to help.
I'm not very familiar with PDB files, but I have done nothing knowingly to change this, and they seem to be in the right place:
I am running out of ideas, but really want to avoid a Windows reinstall if possible.
It's only happening in this one project, so the problem would seem to be with the project itself, not the installation. But I have no idea where to start debugging this problem, or looking for a solution.
Possibly Relevant
I tried running the app on a custom domain (set up in the hosts file and IIS Express's ApplicationHosts.config file). In an attempt to solve this problem I reverted these settings back to the default localhost:[port]. This doesn't seem to have made any difference, but thought I should mention it just in case.
My problem was that the Native Code box was ticked in the Debuggers section of the Web section in Project Properties.
I don't know how this came to be ticked, I certainly never ticked it.
Either way, unticking this box solved my problem.
I'm working on an ASP.net mvc project in Visual Studio 2012. Came across this issue, which is incredibly annoying when debugging my application. Say that I have n number of files open in my editor whenever I build and start a debug-session using F5. Ok, so the editor closes all the open documents as usual, and I do my debuggig tasks. Now; when I stop debugging and want to re-open the files that I had open earlier, I'm not allowed to do so. Nothing whatsoever happens when I click these files, until I restart VS2012.
If I close all of my open documents before debugging, opening them after works fine and the way it's supposed to. Also, this is the case for all of my new or existing projects. I run with ReSharper 7.1.2 installed.
Has anyone encountered this issue before?
To stop ALL files from being closed after debugging simply go to
Tools > Import and Export Settings > Reset Settings
This will fix this bug, I have the old settings saved that caused this error but I am unsure what specifically causes it within the settings. After frustratingly searching around for a clear answer to this problem I hope this helps others that might have this issue.
Note, I also had your error in my instance of VS 2012 but had neither of your extensions. I would propose that uninstalling your extension removed the setting causing the error.
Did you tried cleaning the solution?
Go to Build then click Clean solution
After a bit of trial and error, I found that AnkhSVN was causing the problem.
Whenever I tried to check in (or out) the code, it caused some exception.
I have no clue, why this prohibited me from opening files after debug but it works after removing AnkhSVN.
I've got this issue as well. I wasn't able to solve it. In my case, the file was open but it was invisible. After debugging again with the file still open but "invisible" I got an error that the file doesn't exist when I navigated to the page (I faced this issue while working on an ASP.NET project).
I recommend reinstalling VS, in case you've messed with all the debugging and window settings.
Quite a strange problem I have here, I am trying to run the DXUT DirectX 10/11 tutorials from DirectX sample browser. They build fine, but cannot be run in Debug mode, as this triggers the error warning "Failed to create the Direct3D device". This is strange as I can run them in release mode. The strangest thing however is that they use to run in Debug mode, and I swear I changed nothing in the day it ran, and the next day that it didn't. A friend also has the same exact problem, which happened around the same time.
Has anyone ran into this problem and know of a solution, or perhaps know why its happening beyond the obvious, I have a DirectX 11 capable card if you didn't pick that up.
Thanks.
I literally just spent all day trying to fix this exact same problem. Here is the solution which should hopefully fix yours too...
I managed to find this article explaining that a recent update, (26th February 2013 to be exact), caused the older version to mess up:
http://blogs.msdn.com/b/chuckw/archive/2013/02/26/directx-11-1-and-windows-7-update.aspx
That explains why it was working fine a few weeks ago, and now it just suddenly stopped working I guess!
Following their advice, I downloaded a trial version of Visual Studio 2012, and after an hour and a half of installation time, and a system restart, you should have all the new DirectX SDK files that you need.
NOTE: You don't even have to use Visual Studio 2012. The new files should fix your issues for Visual Studio 2010 and older versions I presume!
(Before doing this I also installed all the latest drivers, but I don't think that did anything to help, but it's worth upgrading drivers whenever you can, as that has fixed a similar issue I had before).
Hope this helps!!! :)
Somewhere in your code you probably have something along the line of this
#if defined(DEBUG) || defined(_DEBUG)
createDeviceFlags |= D3D10_CREATE_DEVICE_DEBUG;
#endif
If you do take a look at the D3D10_CREATE_DEVICE_DEBUG; on the msdn you will see this
To use this flag, you must have D3D11_1SDKLayers.dll installed;
otherwise, device creation fails.
You should check that you do have that dll in your system or you should reinstall the DirectX SDK.
The automatic IE10 update is what caused my issue of automatic non support of directx development. Simplest solution is downloading standalone win8 sdk at...
http://msdn.microsoft.com/en-us/windows/desktop/hh852363
The directx debug layer dll has to be updated.