I would like to use a 3rd party wrapper dll in an asp.net core project. (Emgucv)
The Problem is: The .net Wrapper expects several DLLS in \x86 or \x64 folder in a traditional .net \bin directory.
I tried packing the two folders in a nugetpackage and adding that to my project, but that does not seem to help.
I have no clue how this could work out in asp.net core.... or if there even is a way?
Will it work to create an additional ("oldschool") net dll, handling my 3rd party stuff?
Related
I'm trying to obfuscate my Razor app with SmartAssembly, but I've ran into a problem.
I have lots of Razor (cshtml) pages in my app that all contain references to many different types across the project. This is a problem, because the cshtml files are not compiled during deployment, and the obfuscation process doesn't affect them. This leads to a ton of TypeLoadExceptions and MissingFieldExceptions, because as the cshtml files are being compiled during runtime, the C# code in them references the original, non-obfuscated types.
I've tried enabling PrecompileBeforePublish hoping that it would separate the C# from the HTML so it can be processed by SmartAssembly, but the pages don't seem to be compiled in the build.
Is there a setting somewhere in SmartAssembly that enables Razor support, or can I do something with my ASP.NET Core project to make obfuscation possible?
ASP.NET Core Version: 3.1
SmartAssembly Version: 7.5
I lost one week of development because of not committing my code. I work on a personal project and I lost my code I only have the published version of my asp.net core 3.1 project. and my code is not obfuscated.
I use DotPeek to open my main dll and I get controllers but there are no views in there ? I wonder to know, is there any way for me to create a solution like I had without creating views by my hand?
Is it possible to completely regenerate Visual Studio solution folder for this project from Published files?
I have the source code of a dll project that Targets .NET Framework. And I'm current developing a Universal App, I want to reference that dll to my project but it is not applicable since the Universal App uses a .NET CORE and that dll is specifically targets .NET Framework.
I'm thinking that I can change the dll's Target Framework since I have the source code but I don't know how.
Or is there another way of solving this?
I don't think there's an automated way to convert the library directly (if anyone knows a way, would be more than happy to hear about it).
However, sine you have the source code you can manually move the code.
Create a new Universal Application Class library and start move the code from the old library in there.
Chances are, not everything will work, since there are pretty major differences between namespaces and APIs between .NET framework and .NET core but at least you'll know what you need to change. I would recommend a modular approach where you include portions of the library, make sure it compiles and so on.
I need to use the REST feature, HttpMultipartMimeForm, which I believe belongs to Microsoft.Http.dll. But in my .Net 4.0 project I couldn't find it anywhere. I do have my project's Target framework configured as .Net Framework 4, not ..Client Profile, and as an evidence, I do have the System.ServiceModel.Web assembly in the available .net reference list. But I still don't have the Microsoft.Http.dll and therefore, don't have the class I need. I think I may be able to get the dll if I download and install WCF REST Starter Kit but why do I have to do that? .Net 4 is supposed to have it as part of standard, isn't it?
It's now called MultipartFormDataContent and it is in System.Net.Http. You can get the nuget from here http://nuget.org/packages/Microsoft.Net.Http/2.0.20710.0
I am new to silverlight. I have a silverlight application and i need to refer some 3rd party dll's for some functionality. If i try to add reference for few dll's i get the below error:
You cant add reference as the dll was not built against silverlight runtime.Silverlight projects will work with silverlight only.
For few dll's i get the error below:
A reference to dll cannot be added. Please make sure that the file is accessible, and that it has a valid assembly or COM component.
How do i solve this?
Silverlight has it's own target in .NET. As such, any assemblies a Silverlight application references has to be built with the Silverlight target. Ask the vendor if they have a Silverlight build.