This bounty has ended. Answers to this question are eligible for a +50 reputation bounty. Bounty grace period ends in 14 hours.
Walter wants to draw more attention to this question:
I am trying to do CRUD operations from NFS Drive inside a cluster using .NET7 and C#. What will be the best package or way to implement this feature?
I am looking for a nuget package or library which can help me to connect with a v4 nfs client for my dotnet7 web application using C#.
So far I have found only this library which was last updated about a decade ago:
Nekodrive
Is there any other way to mount/read/write file to nfs using C# and .net7?
The only library I know that is made in 2021 in net standard 2.1 which mean is compatible with .net core 7 is NuGet NFS-Client.
The source code for the solution to be found https://github.com/SonnyX/NFS-Client
As you can see in the code base, it is compatible with version NFS Client v.4 as well as 2 and 3.
I have not used this library before but is suggested by a friend of mine.
Related
I am building an application using AWS SES, but it is not clear to me which version of the API I should be developing against.
AWSSDK.SimpleEmail
AWSSDK.SimpleEmailV2
Looking at the Amazon Simple Email Service Documentation I see both API and API v2 listed.
Logic would tell me to use v2 as that is a higher number, but at the same time the Developer Guide primarily references API (not API v2).
Similarly the Code examples section is much smaller for v2.
If I look at the .NET libraries, which is the SDK I would be using, it isn't much help either, and both versions have had updates pushed in the last 24 hours, and both are on version 3.10X.XX.
Is there any documentation from AWS that indicates the status of their SES SDKs and when particular versions are going to be deprecated? I would prefer not to start developing against a specific version only to find that support is ending for it in a short time.
Thanks
As per https://docs.aws.amazon.com/cli/latest/reference/ses/index.html
AWS CLI version 2, the latest major version of AWS CLI, is now stable
and recommended for general use. To view this page for the AWS CLI
version 2, click here. For more information see the AWS CLI version 2
installation instructions and migration guide.
In other words, I would recommend using version 2.
Now the question you are asking is given the .NET SDK V3, what version of the SES .NET API should you use.
In the AWS Github, it uses SES .NET Service Client v1:
https://github.com/awsdocs/aws-doc-sdk-examples/tree/main/dotnetv3/SES/Actions
However, now there is .NET Service Client v2.
https://docs.aws.amazon.com/sdkfornet/v3/apidocs/items/SimpleEmailV2/TSimpleEmailServiceV2Client.html
Both are supported and I do not think you have to worry about support for v1 ending in the short time. I will confirm and post back.
I'm developing a Blazor PWA project where the WASM client needs to generate PDFs. My employer had already purchased an Xfinium license, thus I have been using it in our project. I have just recently ported the project from .NET Core 3.1 to .NET5 and have begun encountering issues with the Xfinium library. First of all, I am using the Xfinium.Pdf.NET library, as it supposedly supports .NET5. Upon attempting to initialize any object from this library (i.e. PdfFlowDocument test = new();) I am immediately greeted with the following error: Assertion at /__w/1/s/src/mono/mono/mini/interp/transform.c:3592, condition <disabled> not met, which causes my application to crash. To further pinpoint this issue, I created two separate Blazor PWA WASM projects, one with .NET5 and one with .NET6, installed the Xfinium.Pdf.NET library, and attempted to use it. Both resulted in the exact same error as above. I then recreated this on a separate machine as well.
I have reached out to Xfinium support in regards to this issue, and have yet to hear back. Wondering if anyone else has experience a problem similar to this one. For the time being I will simply keep the project on .NET Core 3.1 (the upgrade was to fix another issue where we couldn't read more than 2mb at a time from indexed db database).
Any help is much appreciated!
Upon receiving a helpful workaround from the Microsoft Forums and a response from the Xfinium support team, I can answer my own question.
The Xfinium support team was able to recreate my issue with the obfuscated NET version of their Xfinium.Pdf library. Upon testing the non-obfuscated assemblies of the same library, the problem was non-existant. Therefore, they believe the obfuscation tool is the source of the problem and have notified me that they have reached out to their obfuscation tool vendor. I will be alerted by their support team when the issue is fixed.
As for a workaround, a user named Bruce on the Microsoft Q&A Forums suggested I try the NetStandard version of the library in my NET5 project. This solved my problem. I then alerted the Xfinium support of this solution and they told me that the NetStandard assemblies for this library are in fact obfuscated using a separate tool.
Thus, for the time being, I will be going forward using the NetStandard version of the library. I will update this post when Xfinium support alerts me that a fix has been shipped.
I want to use Google.Apis.AnalyticsReporting.v4 to ETL the google analytics data to our data warehouse. It is worthy to mention that I use SSIS (Microsoft Integration Service) and use Script Component (C#) as task to ETL aforementioned data.
I found this task very hard and find these references,
Use Google Analytics API to show information in C#
It used Google.Apis.Analytics.v3 for doing this and it is not V4. First of all, I create service account,
https://cloud.google.com/iam/docs/creating-managing-service-accounts#iam-service-accounts-rename-console
and save service account email and .p12 key, after that I use this method,
Analytics Reporting v4 with API key
that use Google.Apis.AnalyticsReporting.v4 but many references have errored and they are old, such using Google.Apis.Services;
I confused and want to know the code for ETL the GA data by C#. Appreciate to help me on this issue. I want to ETL metrics like "session" and dimension like "campaign"
I was never able to get it to work using a scripting component because of the .net version of the dlls. The library dlls are around .net 4.5 and as far as far as i could see most versions of MS Sql server dont support higher then .net 4.0. You also have to figure out where the dlls need to be in order for ssis to find them. If your going to get it to work your going to need all the dlls from the library as you cant use nuget install. i would start with the basic tutorial get that working as a console application then copy it over to SSIS and put that into your scripting component you need all the using and their corresponding dlls there is a lot of them.
Google apis.services isnt old its the auth part of the library it just hasnt needed to be changed.
custom component
What I have done was create a custom component to connect to Google analytics. The main issue I had was the dlls and the .net framework. I was never able to use the Google .net client library. I was only able to get this working by manually creating my own Google analytics library targeting .net 3.5 and using Oauth2 rather than service account.
Coding my own service account authentication code has so far escaped me. I beleave i have a very old open question here on stack asking how to get it to work.
Disclaimer: I work at ZappySys
Calling API is possible in SSIS using Script Task by referencing SDK dlls but you have to consider two things.
How much effort needed to code this flow. Some times its not worth it to develop your own if any one already developed such component (Free or Paid).
Is SDK provided by Google is compatible with SSIS version? Each SSIS version supports specific .net version(s). So you must use Google SDK compatible with that. For Example if you like to code this for SSIS 2012 then you must use SDK which is coded in .net 4.0 or Lower version. Using latest SDK might not work sometimes if its coded in .net 4.6 for example.
Here is the list of supported .net versions by various SQL Server / SSIS
SSIS / SQL Server 2012 - Use .net 4.0
SSIS / SQL Server 2014 - Use .net 4.5 or lower
SSIS / SQL Server 2017 - Use .net 4.6.0 or lower
SSIS / SQL Server 2019 - Use .net 4.6.2 or lower
If you do not want to go through hassle you may consider 3rd party components such as ZappySys Google Analytics Source for SSIS
Differing from this question, I realise that Unity uses a modified version of .Net 3.5. Thus I revised available options to one of the following:
1- create a TCP server/client to communicate between library and Unity project
2- Use database as messaging system
My question, is there a simpler way I am missing to get my dll to work on Unity?
Note that I just want my Unity project to build for the Universal Windows Platform
I ended up using signalR as a local communication server between my .NET4.5 code and Unity .NET code.
More information in this blog post
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I have read much of the news around MS open sourcing .NET, e.g. http://blogs.msdn.com/b/dotnet/archive/2014/11/12/net-core-is-open-source.aspx.
However I am still in the dark as to whether MS has released a runtime to run a .NET application on Linux and/or Mac? I still have a number of questions I hope someone can answer:
Can I run my .NET application on Linux/Mac (without mono), if so I read only the "server-side" stack has been open sourced, which assemblies exactly does that entail, can I run a Hello World console application?
Can I include the MS runtime for Linux/Mac (if there is one) with my application so it does not need to be installed separately system wide (like it does on Windows)?
Similarly can I include .NET assemblies without having them installed on the system?
With .NET open sourcing is a MS runtime avaliable on Linux and Mac?
Short answer is soon, they hope to have one completed by Build 2015. If Xamarin/Mono is anything to go by, you might have things like Partial Classes in Platform specific Projects, so when you build your solution you will select which projects (with the platform specific partial classes) to compile to target different OS's.
Long answer, looking at the comments in the link you posted lets us gaze into the crystal ball:
#Rev.pl: Does it mean you'll actually open-source the JIT compiler?
Immo Landwerth: That's exactly what it means. And the GC. And the type system. And the assembly loader. And the assembly binder. And the interop system: we'll open source the entire CoreCLR runtime!
#Dave: does anyone know is plain old WCF a part of CORE?
Immo Landwerth: The client side of WCF will be included in .NET Core.
#Alberto: So WPF will be open source too? :)
Immo Landwerth: A subset of the .NET Framework is released under the MIT license on GitHub.
#ts: Is there a roadmap to "upgrade" WPF to .Net Core 5?
Immo Landwerth: There are currently no plans to port either WinForms or WPF to .NET Core.
... I just want to clarify one thing: just because WinForms and WPF aren't open source doesn't mean we'll not invest in them. In fact we just blogged about our WPF roadmap :-)
Sarat Adiraj
Will System.data (ADO.net) be part of the open sourced server stack ? I don't see any point in having an open sourced asp.net running on linux and Mac if it does not have the corresponding open source bits to connect to database back-ends.
To answer my own query posted earlier I just noticed (github.com/.../DataCommon) System.Data.Common available as part of ASP.net vNext. Great job guys !!
ronelm2000 ... I wonder if XNA Framework gets the hit too?
Me: See http://www.monogame.net/showcase/
Bastion Game Developers: “MonoGame enabled us to painlessly port a full 3D XNA 3.1 game which targeted iOS, MacOS, Linux and Chrome using a fork of the MonoGame code."
Draw a Stickman Epic Developers: “Using MonoGame, we were able to share around 95% of our code between multiple platforms. MonoGame helped us so much, more time was spent getting our game’s content to fit new screen resolutions than actually porting the game to new platforms. Starting out we developed for standard XNA (reach profile) on Windows, then had a pretty easy port to iOS, WinRT (Windows 8) and Android using MonoGame. Many more platforms will follow shortly.”
#Bo: Ok so all of this is leaving me a bit confused. What does all of this mean for me as an LOB developer?
Immo Landwerth: The key difference is that .NET Core will be a single, cross platform stack.
Let's contrast this with .NET Framework and Mono today. Mono is a full reimplementation of the .NET Framework. This means that certain features aren't supported or implemented differently enough to cause behavioral changes that can break your application. Also, Microsoft doesn't support running on Linux or MacOS today.
.NET Core on the other hand will be supported by Microsoft on Windows, Linux and MacOS. We'll have a single code base that we plan on working on together with the Mono community.
For you that means that targeting other platforms will be more reliable and innovation will happen faster. It also means that you'll be able to find out sooner what's coming next because all the design work is happening in public.
Finally, you'll also be able to take a look at the kitchen and engage in design discussion.
As of Nov 21, 2014, the answer is not yet.
We will be working closely with the Mono community as we complete our Linux port.
-Scott Guthrie
That comes from Scott's blog (see the section titled "Bringing Core .NET to Linux and OS X"). They are working to complete it.
Edit
Jeremy Thompson pointed out that they hope to have this completed by Build 2015 (see the section titled ".NET Foundation")