cheers!
Im trying to open new project with visual studio 2010
the version I want to use is 1.0.
so, those are the steps I used to do that:
1. installed windows DDK 7.1.0
2. opened (I tried regular and gstreamer SDK) new project with VS-2010
3. added x86.props (from C:\gstreamer\1.0\x86\share\vs\2010\msvc)
4. added gstreamer-1.0.props (from C:\gstreamer\1.0\x86\share\vs\2010\libs)
5. changed the working directory to "C:\gstreamer\1.0\x86\bin"
6. copied the basic code (Hello World) from here- [Hello World][1]
I did exactly the same thing but with 0.10 (and it worked) and now, with 1.0, when I build the code I get the error:
Error 1 error LNK1104: cannot open file 'gstreamer-1.0.lib'
after I added the "gstreamer-1.0.lib" (from C:\gstreamer\1.0\x86\lib) to "Additional Library Directories"
I got the error:
Error 1 error LNK1104: cannot open file 'msvcrt_winxp.obj'
I will be happy for some guidance of starting new gstreamer project..
Thanks!
The file msvcrt_winxp.obj is part of WinDDK, so it sounds like something has gone wrong with setting up your visual studio project.
First of all, make sure you're using the gstreamer packages from gstreamer.freedesktop.org and not the SDK from gstreamer.com. The SDK is for the older gstreamer 0.10.
Now having just said that, the gstreamer.com website still has some useful documentation on it. I recommend following the instructions at the bottom of this page, under the heading "Creating new projects using the wizard":
http://docs.gstreamer.com/display/GstSDK/Installing+on+Windows
You'll want to click to expand the manual installation instructions in the blue box, as the installer did not automatically copy all the files for me.
Once you've got that set up, make a new project using the wizard and everything should work!
If you're still having problems, check the instructions under "Remove the dependency with the Visual Studio runtime" to make sure you've installed the DDK properly.
Related
I'm going to create my first managed plugin for Unity (2018.2) using Visual Studio Community for Mac (7.6.11 build 9).
I've read the documentation but I think that the step-by-step instructions are not meant to be followed on Visual Studio Community for Mac.
As you can see in the screenshot below, I've created several projects using each and every library template available.
All of them compiled successfully to a DLL targeting versions of .NET framework that are incompatible with Unity.
The only project I could change the .NET framework version to match Unity's 3.5 is the one based on the Other > .NET > Library.
Everything works fine but I'd like to know if the assumptions, the process and the final result are correct. Can you tell me, please?
I don't know the difference between the "Class" and the "Class Library" option but you're supposed to use the "Class Library" option. This is not the main point of this answer.
Two future issues you haven't solved yet:
1. Referencing Unity's API.
If you ever have to use any Unity library or API in youir plugin such as Vector3, you need to add Unity's UnityEngine.dll to your library settings. If you don't, you will run-time exceptions.
Go to Project --> Add Reference ---> Browse ---> Browse Button
then select <UnityInstallationDirecory>\Editor\Data\Managed\UnityEngine.dll. You can now build your managed plugin. Since you're using Mac, this path is different on your OS. On Mac, this could be /Applications/Unity/Unity.app/Contents/Frameworks/Managed/UnityEngine.dll. You just have to find where UnityEngine.dll is located.
2. Invisible stack trace
With your current setup, if you run into error with your managed plugin, the stack trace won't be there. You won't have the file names and line numbers and this makes is very hard to debug your plugin code.
When you build the project, Visual Studio generates a PDB file instead of an MDB file. Unity can't use this directly. You have to convert the PDB files into MDB files.
From command line, run this:
<UnityInstallationDirecory>\Data\MonoBleedingEdge\lib\mono\4.5\pdb2mdb.exe UnmanagedPlugin.dll
Again, the path might be different on Mac, you just need to find "pdb2mdb.exe" that converts the PDB files into MDB files.
After that, copy the MDB and dll file into the "Assets" folder in your Unity project.
I have a project I've been messing with and adding features to, and it was aspnet core 1.1. I am migrating it to 2.0.
I use Visual Studio for Mac, and it's up-to-date.
I am following this documentation:
https://learn.microsoft.com/en-us/aspnet/core/migration/1x-to-2x/
The exact error I'm getting is:
The predefined type `System.Object' is not defined or imported
I found the answer:
In VS for Mac, it didn't let me get to a menu for selecting the target framework for a project. This is usually opened by right-clicking the project, and selecting "properties."
VS for Mac didn't show this.
Upon using my windows install on my iMac, I found the menu and saw AspNetCore2.0 wasn't listed (but 1.0 and 1.1 were). There was also another option to install more. this led me to:
https://www.microsoft.com/net/targeting?utm_source=getdotnetsdk&utm_medium=referral
At this page, there are SDK's for the AspNet Core 2.0 for macOS and windows 64-bit. You need to install these, and then it'll build.
The fact that visual studio doesn't indicate that you're missing a selected framework for the project you're trying to build (as defined in its config file) is absurd. They need to fix this to avoid these kind of headaches. I was under the impression that it wasn't needed, as the NUGET package for 2.0 had all o this.
I have Visual Studio 2010 SP1.
I wrongly edit and save the file
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets
and now I can't compile anymore.
The error I got is
1>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.Targets(767,39):
error MSB4057: The target "_Xsd" does not exist in the project.
I reinstalled Visual Studio 2010, I copied the file from another computer but nothing works and I still have the same error. What can I do?
I search the solution on Internet and i found:
Copy the right target file from another machine to replace the target file.
Uninstall and re-install .Net Framework 4.0 and check if it works.
I tried to restore or install new version of the .NET framework, but other problems occured during installation maybe dued also by hardware problems (i got blue screen sometimes).
I know it isn't a good solution, but at the moment I solved the issue by formatting and reinstalling everything.
I was building/deploying my Windows Phone app in Visual Studio Professional 2013 with Update 3. The following console output showed up:
1>------ Build started: Project: CapturingVideos, Configuration: Debug ARM ------
2>------ Deploy started: Project: CapturingVideos, Configuration: Debug ARM ------
2>Deploying to Phone Internal Storage...
2>Creating a new clean layout...
2>Copying files: Total <1 mb to layout...
2>Checking whether required frameworks are installed...
2>Warning : DEP0810 : This app references Microsoft.Phone.WinJS.2.1, version
1.0.9651.0, found in your SDK, but you have a higher version of
Microsoft.Phone.WinJS.2.1 installed on the target machine, 1.0.9651.40228. If you
continue to run this application, it will run against the currently installed version,
Microsoft.Phone.WinJS.2.1, version 1.0.9651.40228. Consider updating your SDK to match
the version of Microsoft.Phone.WinJS.2.1 that is installed.
http://go.microsoft.com/fwlink/?LinkId=260891
2>Registering the application to run from layout...
I was curious about the Warning which suggested me to update the reference from WinJS.2.1 v1.0.9651.0 to v1.0.9651.40228. So I downloaded and installed the Visual Studio 2013 Extensions for the Windows Library for JavaScript. After restarting the OS and VS 2013, I tried to create a new Windows Phone project from the blank template. I expected the References folder to contain Windows Library for JavaScript 2.1 v1.0.9651.40228. However, it still only point to the old version, which was v1.0.9651.0. Was I on the wrong track or did I miss something? Please point me to the right direction. Thanks!
The issue is caused by wrong App Package Version number which is clearly displayed as 1.0.9651.0 in the reference properties despite all the .js and .css files the package contains have the correct build number 1.0.9651.40228 specified in their headers.
The App Package Version property takes its value from package's manifest file %Program Files%\Microsoft SDKs\WindowsPhoneApp\v8.1\ExtensionSDKs\Microsoft.Phone.WinJS.2.1\1.0\SDKManifest.xml particularly from the following line:
FrameworkIdentity="Name=Microsoft.Phone.WinJS.2.1, MinVersion=1.0.9651.0"
So tick the file's Read-only flag off, open it as an administrator and change the MinVersion number. Reload your solution. The warning message should disappear.
I had the same issue and found this blog post, along with your question here on StackOverflow:
http://blogs.msdn.com/b/lighthouse/archive/2014/04/21/can-t-update-visual-studio-2013-extensions-for-the-windows-library-for-javascript.aspx
I didn't have the issues your describing, or the issues warned about in the blog post, but they explained how to correct them with a powershell script.
Recently I decided to make a switch from OpenCV 2.1 to Opencv 2.4. I am having problems in configuring it with opencv. The details are as follows:-
Installed and extracted opencv in folder( opencv2.4).
Created a new folder "BIN" inside (opencv2.4). Used CMAKE to extract all data in BIN.
While using CMAKE I did not select QT, TBB, IPP options.
I added path to System environment i.e. C:\opencv2.4\build\x64\vc10\bin;
I used the solution in "BIN" folder and compiled first with Debug and then with Release options.
Now I started a new VS2010 project.
In project properties; C++ -> General
In project properties;Linker-> General I did
In project properties;Linker-> Input I did
I finally copied all .dll files in my debug folder.
When I run program, I am getting following error.
I dont know what wrong I am doing. Somehow I think I am not linking the library properly. Plz guide me in this regard . . .
There are extensive tutorials coming with the official OpenCV installation. They explain in great detail, with a lot of screenshots, how you configure Visual Studio with OpenCV. You can read the documentation online. I'll link the two tutorials relevant to this question:
Installation in Windows
http://docs.opencv.org/doc/tutorials/introduction/windows_install/windows_install.html
How to build applications with OpenCV inside the Microsoft Visual Studio
http://docs.opencv.org/doc/tutorials/introduction/windows_visual_studio_Opencv/windows_visual_studio_Opencv.html
You miss the opencv_legacy242.. lib. Add it and try again. Some functionality has moved to legacy in latest release
You may also try follow videos on this subject. They help a lot. Those from a reliable source of course. I know there's one on opencv.org website.