I update support library version to 24.1.1 and now Studio cant find support recourses:
Error:(9, 23) No resource found that matches the given name (at 'icon' with value '#drawable/abc_ic_menu_moreoverflow_mtrl_alpha').
Related
I'm using VS2022, and I received an old project, where iTextSharp was used, but I can't determine a specific version of the mentioned.
I've tried - Tools -> Nuget Package Manager -> Manage Nuget Packages for Solution...
But was unable to find iTextSharp.
Thanks in advance.
It sounds like the assembly has been included directly in the source control, as was common place before nuget. Take a look in your project's references and you should be able to locate the dll. Checking the file's properties in VS should show you the assembly's details in the properties panel and should also show you which version is being used, if not the path or filename may give you a clue as to the version being used.
I read this tutorial to try to set up Vulkan in Visual Studio. I got to the very end, compiled, and got this:
A few more screenshots:
I'm using version 1.1.114.0 while the tutorial is using 1.1.77.0, which may be at the root of the issue. However, I have not been able to find another tutorial showing how to set Vulkan up like this. How do I get Vulkan to work in Visual Studio?
I believe you must have missed a step in the tutorial. Specifically, look for the text
Next, open the editor for library directories under Linker -> General
in the linked tutorial page.
In the linker Input tab, either use a complete path to the Vulkan library (for example C:\VulkanSDK\1.1.101.0\Lib\vulkan-1.lib) or in the General tab, add the location of the library (for example C:\VulkanSDK\1.1.101.0\Lib to the Additional Library Directories entry).
If you can express the values in terms of an environment variable, then you'd want to use either VULKAN_SDK or VK_SDK_PATH, which in the above examples would resolve to C:\VulkanSDK\1.1.101.0. That way when you update your Vulkan SDK you don't need to update your project files, and they'll work on other machines that might have different versions installed.
In the long run I'd recommend switching to CMake for project generation, rather than maintaining Visual Studio project files directly. With CMake, adding a Vulkan dependency to your application is as easy as doing this:
find_package(Vulkan REQUIRED)
target_link_libraries(MyApp Vulkan::Vulkan)
You can find existing CMake-based Vulkan examples here or here.
I am trying to use the hls framework (https://phonesm.codeplex.com/) on Windows 8.0. i have converted HLSView project to Windows 8.0. But Visual Studio tells me that
static readonly IApplicationInformation ApplicationInformation = ApplicationInformationFactory.DefaultTask.Result; does not exist in current context
_mediaStreamFascade = MediaStreamFascadeSettings.Parameters.Create(_httpClients, _mediaElementManager.SetSourceAsync); does not contain a definition for "create"
_mediaElementManager = new WinRtMediaElementManager(Dispatcher, WinRtMediaElementManager could not be found.
I need to integrate this in a Windows 8.0 project. I have read that it is possible, but i don't know how to get past those errors
I have just tried 72bb1b6bb7f3 version (last commit). i have converted hlsview.win81 project to a windows 8.0 project. After commenting SystemMediaTransportControls i only had 2 problems:
Error 7 The base class or interface of 'SM.Media.IMediaStreamFacade' could not be resolved or is invalid c:\Users\Sergiu\Downloads\phonesm-72bb1b6bb7f3885c65e157823b7cf2d341fa5c95\Source\bin\Debug\SM.Media.Platform.WinRT.dll HlsView.Win81
and at mediaElement1.SetMediaStreamSource(mss);
Error 21 'Windows.UI.Xaml.Controls.MediaElement' does not contain a definition for 'SetMediaStreamSource' and no extension method 'SetMediaStreamSource' accepting a first argument of type 'Windows.UI.Xaml.Controls.MediaElement' could be found (are you missing a using directive or an assembly reference?) c:\users\sergiu\downloads\phonesm-72bb1b6bb7f3885c65e157823b7cf2d341fa5c95\source\app\winrt\hlsview.win81\mainpage.xaml.cs 348 39 HlsView.Win81
I don't know how to make it work from here for windows 8.0. Please any help is welcomed
henric (the phonesm creator) answered this question in https://phonesm.codeplex.com/discussions/569208
Basically you have to implement mediastreamsource yourself for windows 8.
I know this will sound quite redundant, but sadly, no answer I have found to this problem online helped me.
I am running Visual Studio 2010, and using the Silverlight 4 SDK (April 2011 version) for my project. (set in the properties, I double-checked)
I did add "using System.Windows.Data;" at the beginning of my .cs file.
Yet, the compiler still gives me "not found" errors concerning my calls to PagedCollectionView.
When I type "System.Windows.Data.", the completion gives me plenty of suggestions, but no "PagedCollectionView"... the first suggestion I get starting with P is "PropertyGroupDescription".
Has this useful tool just been erased out of the surface of the Earth?
Thanks
You need to add a reference to assembly System.Windows.Data for PagedCollectionView.
The namespace System.Windows.Data is used in multiple assemblies for example System.Windows that contains PropertyGroupDescription
Is there any way to use a custom format for assembly versions, when building them with MSBuild?
For example, we tried to use a version like "0.16.10r2.10717" But we got this error:
error emitting 'system.reflection.assemblyversionattribute' -- The version specified '0.16.10r2.10717' is invalid.
I searched around the web, but seems no one asked for a solution of this. Is it possible?
We use Microsoft Visual Studio 2010, and FinalBuilder 7 for building our project.
AssemblyVersion and AssemblyFileVersion both must be composed of up to four integers, period-separated, each of which is no larger than 65534 (UInt16.MaxValue-1). Any of the following are valid (C# syntax):
[assembly: AssemblyVersion("1.2.3.4")]
// Let the compiler generate the build and/or revision numbers
[assembly: AssemblyVersion("1.2.3.*")]
[assembly: AssemblyVersion("1.2.*")]
There is another attribute, AssemblyInformationalVersion, that accepts a string as the version; it can be used when you want to use more complicated strings (especially when including a commit ID from a DVCS).
// Use complex version number
[assembly: AssemblyInformationalVersion("0.16.10r2.10717")]
// Include Git commit ID
[assembly: AssemblyInformationalVersion("1.2b1-g39d1c0f")]
Briefly, the difference between these attributes is:
AssemblyVersion: This is used as the CLR version of the assembly. When the assembly has a strong-name, this is the version that is validated against.
AssemblyFileVersion: This is the Win32 file version resource, and is displayed in the assembly's properties in Windows Explorer.
AssemblyInformationalVersion: This is accessible at runtime via the Application.ProductVersion property. It is also used in the Application.UserAppDataDirectory path.