Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

.NET Core 3.0 Concludes the .NET Framework API Porting Project

github.com

Post reply on HN
Print view View original

151–160 of 317 posts

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#151

Post by UglyToad »

merb wrote: post #149
UglyToad wrote: post #146

Earlier quoted context omitted.

I'm currently building an open source (not copyleft) PDF library for.NET standard [0] and I'd be interested to hear more what you need on the document generation side. The current generation API for my library is extremely limited because I've never needed one but you are the perfect market research participant. It's an API I'm actively looking to improve. PDF/A compliance is probably quite a way off though. [0]: htt…

wow that looks really nice. actually we mostly do html to pdf, but maybe I can look into your project and try to add it (if there is a nice html/dom library like java has with jsoup). basically we don't need a lot, mostly switch fonts/text sizes/images (generated barcodes, logos) and of course pdf/a-3(a/b/u) for invoice. so apis that translate the html into the layouting of pdf is the bigger problem.

Thank you for the response.

Yeah HTML to PDF is a tricky one, presumably wkhtmltopdf/pechkin doesn't work out because of licensing / interop issues? Other than that the only other one I'm aware of is Aspose which is expensive as you say.

Images (along with font subsetting and fixing the gzip implementation) are the next thing I plan to implement so it's helpful to know its a real requirement.

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#152

Post by Someone1234 »

AndrewDavis wrote: post #145
simonh wrote: post #87

Earlier quoted context omitted.

>It means I know where the switches are, and more importantly, what they do Or even more importantly than that, that they even exist in there somewhere.

My goodness. Recently I went to play a game on my laptop, something i don't normally do. I'm not even normally a windows user. It has this 'feature' where if a key is pressed then it disables all mouse clicks for X number of seconds. This is to prevent a forearm from tap to clicking on the touchpad while typing. Absolutely makes sense. Only... I had a mouse plugged in. It disabled a physical USB mouse from clicking a…

This one is mostly the touchpad driver being poorly written and or outdated. Let me guess, Synaptics touchpad?

For some inexplicable reason their newer touchpads (in newer laptops) support the Settings configuration, whereas their older ones (in older laptops) only work via the Mouse Control Panel applet (and sometimes not even then).

I've also had their touchpad driver cause keyboard input latency (it tries to hook hotkeys) with uninstalling it entirely and having no touchpad being the only solution. Their stuff is just bad, and they should feel bad about it.

I doubt they do feel bad as they have a seeming monopoly on Windows laptop touchpads.

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#153

Post by merb »

UglyToad wrote: post #151
merb wrote: post #149

Earlier quoted context omitted.

wow that looks really nice. actually we mostly do html to pdf, but maybe I can look into your project and try to add it (if there is a nice html/dom library like java has with jsoup). basically we don't need a lot, mostly switch fonts/text sizes/images (generated barcodes, logos) and of course pdf/a-3(a/b/u) for invoice. so apis that translate the html into the layouting of pdf is the bigger problem.

Thank you for the response. Yeah HTML to PDF is a tricky one, presumably wkhtmltopdf/pechkin doesn't work out because of licensing / interop issues? Other than that the only other one I'm aware of is Aspose which is expensive as you say. Images (along with font subsetting and fixing the gzip implementation) are the next thing I plan to implement so it's helpful to know its a real requirement.

actually wkhtmltopdf/pechkin both won't support pdf/a-3 and have a not so nice output. aspose is actually really cheap, compared to others, unfortunatly their support is trash: https://forum.aspose.com/t/html-to-pdf-pdf-net-fonts-error-o... i.e. pdf/a-3 does not work on mac (didn't tried linux, but I guess it has similar problems)

btw. itext is a really great library, unfortunatly itext has a problematic licensing and I tought they were jocking after they gave me prices.

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#154

Post by hudo »

jeswin wrote: post #7

Given that our deployment platform was Linux (for a .Net Core 3.0 project), I was determined to use Linux and VS Code for development. That was a fail; the verbose nature of C# and the Framework APIs make it impossible to be productive without significant help from a full-fledged IDE like Visual Studio. One might think the verbosity can be reduced by clever coding (and adopting a functional style), but that's not so…

> - Allow functions outside of classes

use a delegate for this:)

Btw, for dev on Mac I use Jetbrains Rider, its like VS with Resharper or even better. Its also available on Linux. Otherwise, for smaller (micro)services, VS Code works fine. As soon as you start fighting with Code, maybe your solution is too big?

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#155

Post by goto11 »

tonyedgecombe wrote: post #126
surban wrote: post #29

Earlier quoted context omitted.

> My wishlist for C# is short: [...] F# provides all of them, is shipped with .Net Core 3.0 and also works great on Linux.

It doesn't give you structural typing, it's still normative: https://stackoverflow.com/a/3137561/57094

Nominative, not normative. Nominative means "by name", i.e. you reference types by names. A structural type (aka anonymous type) does not have a name, so cannot be referenced.

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#156

Post by tonyedgecombe »

goto11 wrote: post #155
tonyedgecombe wrote: post #126

Earlier quoted context omitted.

It doesn't give you structural typing, it's still normative: https://stackoverflow.com/a/3137561/57094

Nominative, not normative. Nominative means "by name", i.e. you reference types by names. A structural type (aka anonymous type) does not have a name, so cannot be referenced.

Yes, I meant nominative.

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#157

Post by SamuelAdams »

UglyToad wrote: post #146
merb wrote: post #88

sadly .net core still lacks a good pdf library that is not priced over the top. (and at least supports building pdfs and creating pdf/a 3's.)

I'm currently building an open source (not copyleft) PDF library for.NET standard [0] and I'd be interested to hear more what you need on the document generation side. The current generation API for my library is extremely limited because I've never needed one but you are the perfect market research participant. It's an API I'm actively looking to improve. PDF/A compliance is probably quite a way off though. [0]: htt…

In the past I have frequently needed to merge several existing PDF's together. The idea is this: we have a list of objects Foo in a grid that is available to an end user. Each Foo item has a PDF that can be printed - some of our users really like to just look at the paper print out of everything.

So we created a "bulk print" option. They tick a bunch of checkboxes for the Foo items, then click the Print button.

Internally we merge all those PDF's together and send one print job to the printer's queue. We used DevExpress [1] to accomplish this, and it worked very well. The only problem: it's expensive.

Multi-billion dollar companies don't mind paying the price tag, but smaller shops sometimes think twice. If a free or near-free alternative existed, that would be fantastic.

[1]: https://github.com/DevExpress-Examples/how-to-merge-document...

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#158

Post by Someone1234 »

mariusmg wrote: post #9

I've tried to port a MVC project to .NETCore 2 a while ago, it was pretty painful mainly due to lack of @helper syntax in views (everything which relied to @helper had to be changed). Also, from what i saw, nobody is actually in a rush to "move" to .NETCore, most big shops still rely on .Net Framerwork , i still do some occasional work on a project which is using .Net Remoting :)

They're working on bringing back @helper in .Net Core 3 for back-compat:

https://github.com/aspnet/AspNetCore/issues/5110

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#159

Post by privateSFacct »

Question:

I haven’t tried building a windows app in 10 years.

That said, in the past I found it darn easy to wire an interface up quickly.

I recently downloaded visual studio and could not quickly figure out how to get a GUI going (design view would not show).

What is the recommended approach with this new stuff?

Some buttons and textboxes on a form with an onChange method and a data bound grid?

This used to be pretty easy.

Re: .NET Core 3.0 Concludes the .NET Framework API Porting Project

#160

Post by thomasz »

jeswin wrote: post #72
jayd16 wrote: post #35

Earlier quoted context omitted.

The closest you'll get to free floating functions are methods in a static class. The static classes essentially become namespaces. Then with static using directives, you don't need to spell out the namespaces. https://docs.microsoft.com/en-us/dotnet/csharp/language-refe... You can even put every global function into a single class but still organize your code across multiple files by making them all part of the same…

> Then with static using directives, you don't need to spell out the namespaces. Static using directives! Certainly a useful tool, thank you. I had been away from the .Net universe for a while and I think I have some more catching up to do. Some of the newer changes in C# help a lot with reducing code heft, even though it makes the language more complex. However, the Framework seems to be headed in the opposite direc…

The asp configuration thing is complicated but powerful. If you don't want that, you can just use ``Environment.GetEnvironmentVariable`` and be done with it.
Post reply on HN