Graphics-vNext

The future of server-side graphics in ASP.NET

Systems & Infrastructure Creative & Media

Explore on GitHub Read Hacker News discussions

2Distinct people

2Mentions

0Explicit recommenders

67GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

The future of server-side graphics in ASP.NET

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month2 dated mentions

Observed mentions: 2016-01-20 12:06:59 UTC to 2016-09-06 04:36:13 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
Jan 2016	2016-01-01 00:00:00 UTC	2016-02-01 00:00:00 UTC	1	1
Feb 2016	2016-02-01 00:00:00 UTC	2016-03-01 00:00:00 UTC	0	0
Mar 2016	2016-03-01 00:00:00 UTC	2016-04-01 00:00:00 UTC	0	0
Apr 2016	2016-04-01 00:00:00 UTC	2016-05-01 00:00:00 UTC	0	0
May 2016	2016-05-01 00:00:00 UTC	2016-06-01 00:00:00 UTC	0	0
Jun 2016	2016-06-01 00:00:00 UTC	2016-07-01 00:00:00 UTC	0	0
Jul 2016	2016-07-01 00:00:00 UTC	2016-08-01 00:00:00 UTC	0	0
Aug 2016	2016-08-01 00:00:00 UTC	2016-09-01 00:00:00 UTC	0	0
Sep 2016	2016-09-01 00:00:00 UTC	2016-10-01 00:00:00 UTC	1	1

What Hacker News says

2 sources

taspeotis·Sep 6, 2016

System.Drawing is wed to GDI+ so not cross platform. There are third party libraries that work just fine. https://github.com/imazen/Graphics-vNext If you don't care about .NET Core but you do care about ASP.NET Core you can always run ASP.NET Core on Windows and use System.Drawing.

In Lessons Learned while Converting from ASP.NET to .NET Core

NicoJuicy·Jan 20, 2016

This is what i think. .Net ( normal) is Windows only, there's mono which is based on .Net itselve and supports Mac. .Net Core is a extensions on the origin of Mono. Making .Net available on every platform. But Microsoft underestimated the effort it would take. So they are going the .Net Core way for better cross platform support (i'm not saying Mono is bad, fyi!) .Net core is a fork of .Net framework, with support for all platforms ( Windows, Linux and Mac). It tries to support as many things as possible, the hard part is graphics. Which causes problems for WPF and Image processing. Asp.Net MVC 4 - 5 - ... is based on .Net frameworks. Asp.Net 5 is a refactoring of asp.net MVC which supports .Net core and .Net. Which causes difficulty for cross platform support ( some dll's are in a different location using the .Net Core). Also, .Net Core

Read the rest

doesn't support SignalR and image processing ( as mentioned in https://github.com/imazen/Graphics-vNext ) They are now renaming .Net Core to v. 1.0 because there will be some differences between .Net core and .Net and it's more logical, because .Net and .Net core is not the same. But they are looking into it to minimize the differences. Just to be sure, SignalR and Image Processing and graphics problem are going to be solved. Just not yet. Asp.Net Core runs on both .Net framework and .Net core. .Net Core will be used for cross platform development, while .Net framework will be used for Windows Only development ( probably WPF, because it isn't released as opensource yet) Nothing is legacy, Windows has always supported older versions of the .Net framework. I can even run .Net 1.0 on Windows Server 2008... That means a lot. The difficulty for .Net developers is, that .Net core will be using a lot of opensource tools, that they don't have any experience with. You can stick to your old pattern if you want, but i'd advice to learn the new tools, that other frameworks are using ( grunt, gulp, ...) . You would come in contact with them outside of the .Net framework :-)

In ASP.NET 5 is dead – Introducing ASP.NET Core 1.0 and .NET Core 1.0