I have a Windows store DLL which gets the image from the camera device. I want to use this DLL in my driver file[UMDF 2] to get the image. Since the DLL is windows store based DLL, it cannot be directly used in the the driver project. What is the best way to use the Windows store DLL in the UMDF driver ?
Related
I have a .NRY Standard 2.0 Project with a class library where I use the System.DataODBC (installed as Nuget Package) to connect to an Access mdb file.
I then wrote a .Net Framework 4.7.2 console app to test the library and that works as expected. I then wrote a .Net Core 3.0 console app, because the app that in the end will be using the library is a .Net Core app. But this didn't work I get this error:
ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
But I then tried to compile the solution with "x86" instead of "Any CPU" - And that works. I then think it must have something to do with the ODBC driver for 32 of 64 bit?
To be clear I haven't configured any ODBC driver with ODBC admin (odbcad32.exe). I can now run the core Console App in Visual Studio and stand-alone.
But when I put the Core Console app on another machine (a clean install Windows 10 pro in a VM) it still won't work.
What do I have to do/install in the VM machine to get it up running?
If you use mdb (the older legacy JET engine), then you can connect on any machine since a copy of the JET database is shipped with each copy of windows. And YES, you will have to force your project to x32 (x86) since the JET data engnie is only available in x32 versions.
If you use ACE, then you are using the newer ACE data engine which is require if you use the Access 2007 and later format (so for accDB files, you MUST use ACE).
Of course like any drivers or software, if you going to deploy to additional machines, then you have to ensure that ACE is installed. As a general rule, you then have to (should) install the access connectivity components. eg this one:
https://www.microsoft.com/en-us/download/details.aspx?id=54920
Keep in mind that there are two versions of the above. A x64 bit version, and a x32 bit version. You want to continue to FORCE you .net project to x32 or x64, since you can't leave this choice to the wind.
So, you have to include the above install as part of your installer, or simply provide a copy, or have users download + install.
The only way to eliminate the need for above is to go with JET, but that may not be a possible choice for you, and you are restricted to mdb files, and can't use accDB files with JET.
Thanks for the quick answer.
But I found that to run a .Net core app using the System.Data.ODBC the app heve to be compiled for x86 CPU and the server where the app is installed needs to have the .Net Core runtime 32-bit version installed.
i develop an Asp core web application (.net framework).
how i specify a run as 32-bit applications?
the publish wizard do not give way to change the Target Runtime, which the selected option is x64 is selected.
I installed on my machine the x86 version of .NET Core Installer.
publish wizard screenshot:
PS Why do I need x86.
I had to run the site on a computer that installed Microsoft Access 32-bit (2003, for an old software).
I also need to access data in Microsoft Access file, which requires me to use the Microsoft.Jet.OLEDB.4.0 driver.
The problem is, probably, that the app's core ASP.NET always running as 64-bit applications, is what gives me the known exception 'driver not registred'
stil after set "enable 32-bit application" in IIS.
i cant install the 64-bit access driver engine, because it requires the removal of MS Access 32-bit...
As mentioned here you need to add the "runtimes" key to your project.json file like below image.
Once you do this, the Target Runtime entry in Publish menu will list all of your specified runtimes. Although this is not enough to get it working since using the Publish menu and selecting x86 version will have no effect and will result in x64 binary files. (This bug may be fixed in future).
The workaround is to navigate to your project folder where the project.json resides. Open a command prompt and type the following to have your binary in desired runtime:
dotnet publish --runtime win7-x86
If you get any error yet, you may need to have the corresponding runtime installed (Download form here).
More info:
https://learn.microsoft.com/en-us/dotnet/articles/core/app-types
https://learn.microsoft.com/en-us/dotnet/articles/core/rid-catalog#what-are-rids
There is also a platform key under buildOptions listing all possible targets, but yet because of some issues (like #1624) it has no effect and it seems the system ignores that.
In Windows Store apps, either for Windows Phone 8.1 or Windows 8.1 the core metadata file containing all wrapper methods for accessing Windows Runtime API is Windows.winmd.
The question I have is, where is the location of the related XML documentation file, which is generated when building your own library in visual Studio, or in which file is stored the annotation of this Windows runtime library? I've searched in various SDK locations on my PC but found only plain winmd files.
Thanks
i am building a windows 8 store application that will connect to some backend feed. I have all the code in place - but i need to create a package for our test environment and for the production environment. They will obviously use different URLs.
In a normal windows forms/console application i would have one version of the binaries and two app.config files which would host the URLs. As Windows 8 is created as a pacakge - is there any way to have such a config that is not included inside of the package but stored separately and installed during setup? For now the app will not go to the windows store but will be delivered manually to a few devices.
Thanks in advance.
There is no app.config file associated with a Windows Store style app. You could however add an XML file to your app package and access that at runtime with conditional compilation and the ms-appx protocol. But, you would be without all the nice utility functions associated with an app.config.
Because FTP library is not available in Windows Phone 7, and I recently found out that Windows Phone 8 SDK was released, I wonder if it can support FTP library?
You can implement FTP Library. Refer to this article on 'Adding FTP Support in Windows Phone 8' msdn.microsoft.com/en-us/magazine/dn385710.aspx
I'm using the link above and the FTP will not work when bitmap source is set. In other words, if I want to preview a picture before FTP it...it will not work. If not bitmap is set, then FTP works fine.