Which framework/SDK/update or whatever stuff installs this dll?
We've been trying to identify the source of the dll, with Silverlight 4, RIA Services, Silverlight 5 SDK thought of as suspects but apparently none of them are guilty.
Related
I need to consume a library that doesn't yet have CoreCLR support (RabbitMQ.Client, to be specific). Is it possible to utilize a mono-based port of that library on a Linux system from inside a CoreCLR executable? If so, how is that achieved?
It is impossible at binary level (unless using a proper PCL profile). .NET Core has a different approach to arrange classes in assemblies, so some assemblies on desktop .NET Framework are broken into smaller assemblies, and types are moved. A desktop targeting assembly (from .NET or Mono) won't work on .NET Core due to such changes.
But it is obviously possible at source code level, as there was an attempt to port Mono's WinForms to .NET Core,
http://forums.dotnetfoundation.org/t/anyone-porting-winforms-mono-to-net-core/898/4
Once a new .NET Core library project is created, the source files should be able to be carried over (with some modification or even none).
However, .NET Core has been evolving too fast, and that attempt might be now out of date. Anyone would like to explore in this area can follow that example and try once again. Good luck.
I have a static class that uses
System.IO.Path
System.IO.Directory
System.IO.File.
Currently, the class is in my iOS project and unchanged also in my Android project.
I created a PCL that targets Android and iOS only.
However, neither one of the namespaces is available.
I presume that is because iOS and Android alone are not suitable for a PCL profile and that's why Windows Store 8 or Silverlight 5 gets added and that removes the System.IO.* namespaces.
Is this working as designed? Is file linking my only chance in this case?
Yes, for now this is the way it's supposed to work. You can use something like my PCL Storage library to access the file system from a PCL, or you can simply use file linking.
As a side note, I'd recommend choosing Windows Store and .NET 4.5 along with the Xamarin targets. That profile is going to give you more APIs than the one which targets Silverlight 5 which you get by default when you just choose Xamarin platforms in that dialog.
System.IO.Path, System.IO.Directory and System.IO.File are partially supported in PCL profile EXCLUDING silverlight 5: WP8 + NET4.5 + Xamarin + iOS.
Path.Combine works perfectly in this targeted PCL.
My Unmanaged VC++ MFC (No .NET used, No CLR support, Use MFC in shared DLL) application trying to deploy with visual C++ runtime files as private assemblies.
It is properly running on windows 7 fresh installed computer.
But I gives “This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.” error in fresh installed wondows XP sp3 computer.
I checked in application event logs. But there also no more details, just showing the same error.
Then I read these threads and surf around the internet.
Thread - 1
Thread - 2
Article -1
But couldn't find any solution clue or trouble shooting method. so here looking for some assist.
The easiest way to test is to install depends on the computer. Most likely, your application is built to use a later version of C++ runtime libraries, e.g. <assemblyIdentity type='win32' name='Microsoft.VC80.CRT' version='8.0.50727.4053' processorArchitecture='x86' publicKeyToken='1fc8b3b9a1e18e3b' />, but on the XP system it is an older version.
You would need to check what version of the runtime library used by analysing the program's manifest. Then check what depends is showing.
If the required version of runtime is missing, distribute it with the program's install.
On the side note, you could consider switching to the static link. The size of the binaries will be bigger, but these type of problems will be gone
I want to run my c# application with OS Linux using Mono. I am new to this cross platform migration? Please tell the procedure for doing that?
Thanks & Regards.
It very much depends on what type of application it is. For a console or WinForms app, it may be simple. Mono doesn't support WPF.
Well, the first think you'll need to do is install Mono of course. Then you probably want to run MoMA to determine your application's compatibility. There's a whole separate page about porting WinForms apps.
If all is well, you should just be able to run your application using:
mono MyApplication.exe
after copying the binaries over.
If your application is actually a web service or web application, you'll want to think about the various hosting options.
I suspect you'll want to read a lot of the pages on the Mono Start Page.
Check if your application is 100% compatible with Mono Framework using MoMA.
Remove or replace those unimplemented parts with Mono's implementation or third party libraries that works with Mono. Or if you think it should work fine, just execute it with Mono Framework 2.8 or higher. Better go with 2.10 which is default's profile is on 4.0.
There is an IDE, MonoDevelop that supports Web and Desktop applications. Open the project files (monodevelop supports visual studio project files) from monodevelop, compile and run.
you can browse mono website here, where you can find which features are supported and which are not supported and why.
What is the best way to deploy a couple of asmx webservices to IIS. (6.0, 6.1, 7.0)
The services are an optional install and I think the most convenient way to install them would be some kind of Windows Installer package.
I created a small C# program that directly modifies the IIS Metabase, but this only works on IIS 6.0 and 6.1 and I don't want to ship something that might harm a customers IIS installation.
Our services (~10 different .asmx files) are all precompiled and organized in the following structure:
/services
/serviceA
/bin
Service.asmx
/serviceB
/bin
Service.asmx
/serviceC
/bin
Service.asmx
...
..
.
WiX is really best tool to do any kind of software deployment on the Windows platform. Among other things, it includes custom actions for this kind IIS configuring, see XML elements <iis:WebServiceExtension>, <iis:WebSite>, <iis:WebVirtualDir> and <iis:WebApplication> for details.
I did this a long time back (XP) using VBScript and the VS installer?
Id imagine there is a much nicer way to do this now