Where communities thrive

Join over 1.5M+ people
Join over 100K+ communities
Free without limits
Create your own community

Explore more communities

dotnet/home

This is the hub for all the projects that are part of the .NET Foundation. MD files in the projects folder feed the content on the .NET Foundation website

People

Repo info

Activity

Dec 05 19:10

onovotny removed as member
Dec 05 19:10

jongalloway removed as member
Nov 17 05:53

NextTurn opened #155
Nov 16 15:59

NextTurn opened #154
Nov 15 00:13

jongalloway on master

Update new-projects.md (compare)
Nov 14 16:22

NextTurn opened #153
Nov 14 16:00

NextTurn opened #152
Nov 09 20:22

jongalloway added as member
Nov 08 23:32

onovotny on master

Update RxUI license to reflect … Merge pull request #151 from on… (compare)
Nov 08 23:32

onovotny closed #151
Nov 08 22:56

onovotny edited as member
Nov 08 22:54

onovotny edited as member
Nov 08 21:35

onovotny added as member
Nov 08 20:15

onovotny edited #151
Nov 08 20:13

onovotny opened #151
Nov 07 06:47

gep13 commented #150
Nov 07 05:43

jongalloway on master

(GH-111) Update SourceLink loca… Update README.md Co-Authored-B… Merge pull request #147 from ge… (compare)
Nov 07 05:43

jongalloway closed #147
Nov 07 05:42

jongalloway on master

Add new Cake Maintainer Merge pull request #150 from ge… (compare)
Nov 07 05:42

jongalloway closed #150

AAA BBB

@aaabbbcccddd00001111

Hello. .NET, a developer platform for building apps, needs to have an editor provided as part of .NET release. VSCode is an excellent choice. VSCode would need to provide first class support for .NET.

Artemov Ivan

@ZOXEXIVO

Why dotnet publish do not copy wwwroot to output with -runtime linux-x64, but win10-x64 - is ok?
dotnet publish -c Release -o out -r linux-x64 --self-contained true /p:PublishSingleFile=true /p:PublishTrimmed=true /p:PublishReadyToRun=true

TeBeCo

@tebeco

is your csproj web sdk ? first line of the csproj itself

Artemov Ivan

@ZOXEXIVO

Is it Microsoft.NET.Sdk.Web (Blazor Server App template)

I change only runtime identifier to linux-x64 and wwwroot not copying

TeBeCo

@tebeco

got no idea out of this one, i suggest you to open an issue on blazor repo if it's specific to blazor SDK

also it's surprising that blazor that is a "client" tech has a wwwroot

blazor server side might be a bit tricky then

Artemov Ivan

@ZOXEXIVO

stop, of course - it's my bad

TeBeCo

@tebeco

Artemov Ivan

@ZOXEXIVO

i just migrated my angular app and i have wwwroot in gitignore.
Local build works ok, but build on Linux server use git)

TeBeCo

@tebeco

;)

Artemov Ivan

@ZOXEXIVO

Thanks

TeBeCo

@tebeco

glad you found it ^^

Marvin Rühe

@Marv51

Hi everyone!

Quick question: is the Windows.Foundation.Collections namespace still closed source? Where would I report a bug or feature request?

Karel Zikmund

@karelz

@Marv51 yes, closed sourced. Report maybe through some Windows feedback channel? (no idea)

Marvin Rühe

@Marv51

@karelz Thank you!

prog20901

@prog20901

Can someone please help me with your valuable feedback about https://jio.nexedi.com/ ???? Planning to build a full text static search engine for the given files....

muzharab

@muzharab

Hello. Would appreciate any advice on how to improve the throughput performance of a gateway-like service with requests that have a lot of data. Currently simply copying HttpWebRequest stream to context.Request.Body (OWIN).

TeBeCo

@tebeco

Migrate to aspnetcore on dotnet core would be a huge throughput performance gain
Does that count ^^ ?

muzharab

@muzharab

Yes, I believe it does. So there is a big performance difference?

TeBeCo

@tebeco

Kind of a huge one based on the assumption that you don’t have a bottleneck in your code base
By that I mean that if what is slow is, for example, a hot path using explicit lock() it won’t save you

But it will be a rather great improuvment for both throughput and memory allocation (so less GC hit => less “freeze the world”)

But it means you’ll have to rewrite your app to be aspnetcore compliant
And your third part netstandard/netcore compliant

muzharab

@muzharab

ok. Yes, there will be some challenges with porting because of library-dependencies. Thank you very much for the suggestion.

Markus Schaber

@markusschaber

We just upgraded our dev machines from VS 2017 to VS 2019. Now, during debugging, the "Tasks" View does not work anymore, showing the following message:

Viewing Task information for .NET Core 2.2 is not supported while the process is running. You can either re-target a newer version of the runtime, or view task information for minidumps of .NET Core 2.2.

Actually, the project is targeting .NET Core 2.1 (which is LTS version!), and one of the two affected machines has neither 2.2 SDK nor 2.2 runtime installed.

What's happening here, and how to fix it (except downgrading to VS 2017)?

TeBeCo

@tebeco

Out of curiosity
What about 3.0 ? 3.1 preview (next lts)
Are you using vs2019 preview ?
Did you created a feedback hub issue ?

Markus Schaber

@markusschaber

3.0 is installed, it came with VS 2019.
We're on VS 2019 Professional 16.3.9.
I did not yet create a feedback hub issue.

I'll do so now.

无限风灵

@WuLex

what ？

dude

Markus Schaber

@markusschaber

For the record: The issue is https://developercommunity.visualstudio.com/content/problem/821903/viewing-task-information-for-net-core-22-is-not-su.html

Markus Schaber

@markusschaber

@WuLex I'm not sure what you mean?