My shared project has no packages.config, so where is it storing the packages that it uses?
Also, when I edit references, the tabs are empty - I can't select anything.
What's going on here?
Shared Projects let you write common code that is referenced by a
number of different application projects. The code is compiled as part
of each referencing project and can include compiler directives to
help incorporate platform-specific functionality into the shared code
base.
Source: official documentation where you could find all the details. Beside that there are few related thread on SO, like this one.
P.S.: Official Xamarin documentation nicely covering the code sharing options.
Related
Background
We are looking to permit 3rd parties to upload compiled .NET.Core assemblies as plugins into custom AssemblyLoadContexts.
Objective
But the assembly needs the for security issues first, and if it fails, dumping the whole context.
Examples
For example:
we may want the Plugin to only Reference Assemblies that contain APIs, and not lower assemblies that provide integration services (to the db, etc.)
we may want to exclude the assembly if it is making calls to any type that has System.IO for example.
Spot the use of new() so we can log what they are instantiating via an override of IServiceDepency?
We'll learn, and the list will grow over time...
Constraints
Preferably, we'd like to do the inspecting with framework and/or freely available packages, rather than as per: Inspecting contents of compiled assemblies
Questions
Can Roslyn be used for decompilation -- or is it only a code compiler?
Could anyone point to a very simple example to get started?
Thank you!
Roslyin is a compiler technology and can't decompile compiled code.
You can look at the compiler code and learn the IL generation patterns to decompile the code or use something like ILSpy.
I took over a Xamarin project that was previously outsourced to a 3rd party. Oh boy, what a nightmare. There is a portable c# project that is refrenced in a separate Android project. Whenever I try to fix the broken reference I'm getting this error message:
Taking a look at the project properties, I can see that there is nothing targeting Xamarin.Android which I'm assuming should definitely be there since this library is clearly being referenced in a Xamarin project. By the way, there is a separate project for iOS that also references this portable library so I'm assuming Xamarin.iOS will also have to be targeted. Completely baffled here all information from Google has been useless.
I have looked at:
https://learn.microsoft.com/en-us/dotnet/framework/cross-platform/portable-class-library
https://lastexitcode.com/blog/2014/11/16/InstallingPortableClassLibrariesForXamarinStudio/
and all related linked in those pages and endless google searches frustratingly obscure topic.
Taking a look at the packages.config I can see these types targeted as well but again have no idea how these are linked to this package.config.
Are my assumptions correct and how on earth can I add these targets?
It started as simple as that I would like to look up all possible providers. Which ones are allowed?
However, where is the full struct definition?
There isn't a place that I am aware of where the documentation is hosted outside of the GitHub repo here.
I just dig through those and the actual implementation files if needs be to figure out what is available to me if I'm looking for/at new features.
As of WWDC 2019 there is now documentation on Apple's developer website for the package manager. It is here at the time of updating this.
I am pretty new to mvc but have already read a few books.
What I want to archive is:
-> Having the main asp.net app in its own project.
-> Every modul (for example forum modul) is hosted in a regular dll (including its controller, models and views).
I've looked into the issue of hosting controllers in different assemblies. This is actually easy to handle. But what I do have issues with are the views.
I could not find any resource regarding how to tell mvc that he should look for the views in this namespace the the other view in the other namespace.
Best regards
Simon
Have you imported the projects/assemblies in the project you need to use them?
Look in the References folder. They must be there so you can use them.
I am not quite clear why you would use this style of architecture, but again that's your choice.
What I can confirm is that it is not going to be as useful as you think.
A detailed explanation is here
In the official documentation is just shown code with explanations not about a project apart. My question is: Do I need to create a stand alone project which will contain interface and plugin class? And which project template should I use? C++ library?
Knowing Qt's plugin architecture is probably not going to help you much when extending a 3rd party application. The application will undoubtedly have wrapped that mechanism for it's own usage patterns - assuming that the application is even extendible.
So to answer your question directly: The application you are developing for should have it's own API and documentation for extending it, reading that will give you the answers you need.