text:
Failed to Run

Severity	Code	Description	Project	File	Line	Suppression State
Error	MSB3073	The command "dotnet "C:\Users\liudm.nuget\packages\microsoft.aspnetcore.blazor.build\3.0.0-preview5-19227-01\targets../tools/Microsoft.AspNetCore.Blazor.Build.dll" write-boot-json "obj\Debug\netstandard2.0\BlazingPizza.Client.dll" --references "C:\Users\liudm\Downloads\blazor-workshop-master\src\BlazingPizza.Client\obj\Debug\netstandard2.0\blazor\bootjson-references.txt" --embedded-resources "C:\Users\liudm\Downloads\blazor-workshop-master\src\BlazingPizza.Client\obj\Debug\netstandard2.0\blazor\embedded.resources.txt" --linker-enabled --output "C:\Users\liudm\Downloads\blazor-workshop-master\src\BlazingPizza.Client\obj\Debug\netstandard2.0\blazor\blazor.boot.json"" exited with code -2147450730.	BlazingPizza.Client	C:\Users\liudm.nuget\packages\microsoft.aspnetcore.blazor.build\3.0.0-preview5-19227-01\targets\Blazor.MonoRuntime.targets	633

Microsoft Windows [Version 10.0.17134.706]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\Users\liudm>dotnet --info
.NET Core SDK (reflecting any global.json):
Version:   3.0.100-preview4-011223
Commit:    118dd862c8
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.17134
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\3.0.100-preview4-011223\
Host (useful for support):
Version: 3.0.0-preview4-27615-11
Commit:  ee54d4cbd2
.NET Core SDKs installed:
1.0.0-preview2-003131 [C:\Program Files\dotnet\sdk]
2.1.2 [C:\Program Files\dotnet\sdk]
2.1.201 [C:\Program Files\dotnet\sdk]
2.1.202 [C:\Program Files\dotnet\sdk]
2.1.300 [C:\Program Files\dotnet\sdk]
2.1.402 [C:\Program Files\dotnet\sdk]
2.1.403 [C:\Program Files\dotnet\sdk]
2.1.500 [C:\Program Files\dotnet\sdk]
2.1.502 [C:\Program Files\dotnet\sdk]
2.1.503 [C:\Program Files\dotnet\sdk]
2.1.504 [C:\Program Files\dotnet\sdk]
2.1.505 [C:\Program Files\dotnet\sdk]
2.1.600 [C:\Program Files\dotnet\sdk]
2.1.601 [C:\Program Files\dotnet\sdk]
2.1.602 [C:\Program Files\dotnet\sdk]
2.1.700-preview-009597 [C:\Program Files\dotnet\sdk]
2.1.700-preview-009601 [C:\Program Files\dotnet\sdk]
2.1.700-preview-009618 [C:\Program Files\dotnet\sdk]
2.2.100 [C:\Program Files\dotnet\sdk]
2.2.102 [C:\Program Files\dotnet\sdk]
2.2.200 [C:\Program Files\dotnet\sdk]
2.2.201 [C:\Program Files\dotnet\sdk]
2.2.202 [C:\Program Files\dotnet\sdk]
2.2.300-preview-010046 [C:\Program Files\dotnet\sdk]
2.2.300-preview-010050 [C:\Program Files\dotnet\sdk]
2.2.300-preview-010067 [C:\Program Files\dotnet\sdk]
3.0.100-preview-010184 [C:\Program Files\dotnet\sdk]
3.0.100-preview4-011223 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.0-preview2-final [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.0-preview2-final [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.0.0-preview4-19216-03 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 1.0.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 1.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 1.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.0-preview2-26406-04 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.0.0-preview4-27615-11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.0.0-preview4-27613-28 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
To install additional .NET Core runtimes or SDKs:

Getting same thing...
Severity	Code	Description	Project	File	Line	Suppression State
Error	MSB3073	The command "dotnet "C:\Users\lance.nuget\packages\microsoft.aspnetcore.blazor.build\3.0.0-preview5-19227-01\targets../tools/Microsoft.AspNetCore.Blazor.Build.dll" write-boot-json "obj\Debug\netstandard2.0\BlazingPizza.Client.dll" --references "C:\Users\lance\Source\Repos\blazor-workshop\save-points\00-Starting-point\BlazingPizza.Client\obj\Debug\netstandard2.0\blazor\bootjson-references.txt" --embedded-resources "C:\Users\lance\Source\Repos\blazor-workshop\save-points\00-Starting-point\BlazingPizza.Client\obj\Debug\netstandard2.0\blazor\embedded.resources.txt" --linker-enabled --output "C:\Users\lance\Source\Repos\blazor-workshop\save-points\00-Starting-point\BlazingPizza.Client\obj\Debug\netstandard2.0\blazor\blazor.boot.json"" exited with code -2147450730.	BlazingPizza.Client	C:\Users\lance.nuget\packages\microsoft.aspnetcore.blazor.build\3.0.0-preview5-19227-01\targets\Blazor.MonoRuntime.targets	633
This thread was started 6 days ago...  Would have thought that there would have been -some- response since then...  Please let us know how to proceed to get this very cool looking demo running!! :)

Ok -- solved by reinstalling the latest "SDK 3.0.100-preview5-011568" -- if others come across this issue, would suggest doing the same...  @ https://dotnet.microsoft.com/download/dotnet-core/3.0

@lancelarsen thanks yo, this resolved the issue for me.

Thanks, preview 5 is in fact required. I'm updating the directions to be more explicit.

authors: PeterJD lancelarsen rynowak steviecs

repo: dotnet-presentations/blazor-workshop


text:
Clarify type binding capabilities of the configuration binder

Upon installing FxCop analyzers and being presented with the "do not store url properties as strings" warning, I learned that I could just make the property of the class I was binding my configuration to be a System.Uri and valid Uris would magically work. Separately, a colleague suggested we stop using "MyTimespanConfigMinutes=5" for TimeSpan-bound configuration and instead use "00:05:00" based on the guidance here: https://blog.ploeh.dk/2019/11/25/timespan-configuration-values-in-net-core/. This also worked magically. Having two surprisingly magic cases of non-POCO bindings, I investigated more and found that you can actually bind to anything that supports converting from a string due to the use of System.ComponentModel.TypeDescriptor.GetConverter(propertyType) here: https://github.com/dotnet/extensions/blob/master/src/Configuration/Config.Binder/src/ConfigurationBinder.cs#L508-L513.
I think this is extremely useful information that should be documented so that people see that they can use TimeSpan, Uri, and many others out of the box (its also useful to know that this kind of conversion is used, rather than IConvertable conversion or the System.CommandLine approach of allowing anything with a constructor that takes a single string). Finally, https://docs.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2013/ayybcxe5(v=vs.120) is linked to by the TypeConverter docs and its a useful resource, but it should probably be modernized and moved out of the VS 2013 docs into somewhere more discoverable.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0eb4d762-3910-2c57-8741-3306c15537b6
Version Independent ID: ba2254a0-ea8e-9b28-e94b-edd0fc58c043
Content: Configuration in ASP.NET Core
Content Source: aspnetcore/fundamentals/configuration/index.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @jackhorton ... You lost me a bit with "non-POCO" language when it seems like you're just describing property types of POCOs that are supported by the OOB config binder. I suppose that we could describe in a little more detail here which ones are supported OOB. Note that I'm going to have to backlog this quite a bit out because we're all 🏃😅 for the foreseeable future with high priority work on a number of fronts. I can't really say when I'll be free to work this one.
WRT TypeConverter ... that's more of a custom model binding subject. I'm not very familiar with what we have, since I've only glanced at and lightly touched https://docs.microsoft.com/aspnet/core/mvc/advanced/custom-model-binding over the past few years. On a slightly related note, I do have a plan to investigate adding TypeConverter content for Blazor binding (Creating Dynamic component with databinding from datatable (ADO.NET)). It might be best for you to look at the custom model binding topic and see if it covers what you're suggesting. If not, then mention your request on a new issue opened from the bottom of that topic.

As far as I could tell, the configuration binding code and MVC model binding code were completely different (perhaps they shouldnt be, but thats definitely a separate issue). Since there are already sections on the page for binding configuration to arrays and POCOs, I was just hoping to get a blurb slotted in about binding to arbitrary types using type converters. I would be willing to make a PR to add such a blurb, I just thought I would make the issue first to ensure I wasn't missing any context.

Yes, they are different. I just meant that that's the context where TypeConverter normally comes up, and I really don't know/recall what that doc says or shows on the matter. I'm 🏃 right now with high priority work, so I didn't even look.

a blurb slotted in about binding to arbitrary types using type converters

Maybe, but I think you should paste about what you're suggesting in here. If your suggestion is just to mention it, I don't think that's enough to be of any use to anyone. I have a feel'in that an example is going to be required for something that doesn't bind OOB ... such an example might make this long and complex and thus be better suited for a community blog post as an advanced scenario.

@serpent5  please review.

There's an open issue being tracked in https://github.com/dotnet/AspNetCore.Docs/issues/16319 for covering how this works with custom model-binding.

Finally, https://docs.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2013/ayybcxe5(v=vs.120) is linked to by the TypeConverter docs and its a useful resource, but it should probably be modernized and moved out of the VS 2013 docs into somewhere more discoverable.

"Configuration in ASP.NET Core" and "Custom Model Binding in ASP.NET Core" could both link to this, whether it's that version or a newer, better-placed version. It doesn't seem like that topic should live within the docs here, as it's not part of ASP.NET Core.

@serpent5 Thanks

That issue discusses the ASP.NET MVC model binder, this issue is for the IOptions binder. They are different implementations and you can easily use Microsoft.Extensions.Options without touching ASP.NET (which is what we are doing). I dont think this issue should be closed.

Maybe, but I think you should paste about what you're suggesting in here. If your suggestion is just to mention it, I don't think that's enough to be of any use to anyone. I have a feel'in that an example is going to be required for something that doesn't bind OOB ... such an example might make this long and complex and thus be better suited for a community blog post as an advanced scenario.

I'd echo this from @guardrex. Just stating that TypeCoverters are used for certain types, but without covering how to write and integrate your own, might leave things incomplete. It could also prove difficult to try and provide an exhaustive list of what's supported OOB here, especially as it's going to overlap with the custom model-binding topic. For example, if this configuration topic covers how a timespan can be specified in specific formats, that information would also be the same for model-binding.
For me, I see a relationship where this topic and the model-binding topic both highlight that TypeConverters are used and link to a common topic that covers the details of what is supported and how to roll your own. I can't speak for whether that's something this docs team has the capacity for, though.

I know that I'd like one example in the Blazor docs for a use case that a dev asked about ... binding directly to a datatable, which should demo the general approach in such Razor component scenarios. It's a low priority issue tho, so I wouldn't get to that one for quite a while. I see an 🌊 ocean of work 🌊 ahead of me. 🏃🏃🏃🏃🏃🏃🏃

source: gharchive/issue

authors: Rick-Anderson guardrex jackhorton serpent5

license_type: permissive

license_source: github-api


text:
Add LDAP lookup config examples

Add LDAP lookup config examples for RC2

@blowdart  can you accept |reject my suggestions? Do we need to wait for @Tratcher  approval?

It'd be @JunTaoLuo approval not Chris :)

OK I think that's it though. I can't approve my own PR ;)

source: gharchive/pull-request

authors: Rick-Anderson blowdart


text:
Update appsettings.Development.json

Added text as per given instruction in #29512
Fixes #29512

Internal previews

📄 File
🔗 Preview link

aspnetcore/tutorials/grpc/grpc-start.md
Tutorial: Create a gRPC client and server in ASP.NET Core

Testing through this in a moment...

authors: postmeback wadepickett


text:
use correct "after" image

the after image was wrong.

closed, because it's a duplicate of https://github.com/dotnet/AspNetCore.Docs/pull/31802


text:
invalid JSON: got EOF while reading request body when executing CommitContainerChanges

Output of dotnet --info:
.NET SDK:
 Version:   7.0.203
 Commit:    5b005c19f5

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.22621
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\7.0.203\

Host:
  Version:      7.0.5
  Architecture: x64
  Commit:       8042d61b17

.NET SDKs installed:
  5.0.408 [C:\Program Files\dotnet\sdk]
  6.0.408 [C:\Program Files\dotnet\sdk]
  7.0.203 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.16 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 7.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.16 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 7.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.15 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.16 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 7.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
  x86   [C:\Program Files (x86)\dotnet]
    registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables:
  Not set

global.json file:
  Not found

Learn more:
  https://aka.ms/dotnet/info

Download .NET:
  https://aka.ms/dotnet/download

What version of Docker.DotNet?:
3.125.14

Steps to reproduce the issue:
Execute CommitContainerChanges with Docker Desktop for Windows, Version 4.19.0 (106363)
with the following parameters:

ContainerID: Id of a running container
RepositoryName: mcr.microsoft.com/mssql/server
Tag: 2019-CU15-ubuntu-20.04-20230502040827

What actually happened?:

What did you expect to happen?:
New image is created from running container
Additional information:
I feel like it worked up until the last Docker Desktop update (this is only a hunch however).

After downgrading to 4.18 everything seems to work once again. I have however not enough knowledge with the docker API to understand if this is related to an Issue in the Library or Docker itself.

I have debugged HttpConnection. Docker.DotNet sends
POST /commit?container=939eab072cd3cb77123d178c78ed872fe36194fde949ffd737c330198b2ee95f&repo=docker%2Fgetting-started&tag=latest-20230510102730 HTTP/1.1 User-Agent: Docker.DotNet Host: docker_engine:80 Connection: close
and gets
HTTP/1.1 400 Bad Request Api-Version: 1.42 Content-Type: application/json Date: Wed, 10 May 2023 20:29:25 GMT Docker-Experimental: false Ostype: linux Server: Docker/23.0.5 (linux) Connection: close Transfer-Encoding: chunked
in return.
My issue is fixed however, as soon as I set Config to new Config everything works fine. Maybe the fallback here should be an empty object instead of null?

Is this fixed in the library, or is this just a workaround?  I ran into this today and used this workaround as well and it works.  I feel like if this hasn't been fixed it shouldn't have been closed.

I added PR#636

license: MIT


text:
[5.2] Test fixes to accommodate recent infra changes

These changes also include a fix for #2563 since without the changes from #2380 in the 5.2 branch, #2563 + switch to AAD auth in the pipeline results in ConnectionTimeoutInfiniteTest failing. Main still needs the fix for #2563. Ported the same fix to main: #2651

I'm not sure why the CI integration isn't showing up here. It appears to have stopped this morning, so I re-ran it manually.

@DavoudEshtehari Clean! 🎉

"without the changes from https://github.com/dotnet/SqlClient/pull/2380 in the 5.2 branch"

Does it mean that PR 2380 will not go in v5.2.2 release?
Kindly share ETAs for PR 2380 to be consumable, thanks a lot

@yuanhe772 #2380 is in the list of backports and will be included in the 5.2.2 as well.

authors: David-Engel DavoudEshtehari yuanhe772

repo: dotnet/SqlClient


text:
Unable to mount volume error when deploying AspireShop sample

Hi @DamianEdwards,
I am getting this error in the container logs after deploying the sample. to Azure.  The same error occurs on all containers that rely on the persistent volumes (Az Fileshares).
This may be related to this issue.
Thinking of tinkering with the generated deployment manifests in Bicep, but keen to hear ideas!  Thanks.
basketcache
{"TimeStamp":"2024-04-17 15:24:37 \u002B0000 UTC","Type":"Warning","ContainerAppName":"basketcache","RevisionName":"basketcache--pw2dqfs","ReplicaName":"basketcache--pw2dqfs-7fbdff6678-q4jmn","Msg":"MountVolume.SetUp failed for volume \u0022basketcache-aspireshopapphost-basketcache-data\u0022 : rpc error: code = Internal desc = volume(csi-013e9aa7c10952d1a636d63d7aaf6638b79c7a8a946084ae614a1b1913da6990) mount //voloplsf5k257d5c.file.core.windows.net/basketcache-aspireshopapphost-basketcache-data on /var/lib/kubelet/pods/37796c77-df8e-4a88-b6cd-1d5ac12f4991/volumes/kubernetes.io~csi/basketcache-aspireshopapphost-basketcache-data/mount failed with mount failed: exit status 32\nMounting command: mount\nMounting arguments: -t cifs -o ,file_mode=0777,dir_mode=0777,actimeo=30,mfsymlinks,nosharesock,\u003Cmasked\u003E //voloplsf5k257d5c.file.core.windows.net/basketcache-aspireshopapphost-basketcache-data /var/lib/kubelet/pods/37796c77-df8e-4a88-b6cd-1d5ac12f4991/volumes/kubernetes.io~csi/basketcache-aspireshopapphost-basketcache-data/mount\nOutput: mount error(2): No such file or directory\nRefer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)\n\nPlease refer to http://aka.ms/filemounterror for possible causes and solutions for mount errors.","Reason":"FailedMount","EventSource":"ContainerAppController","Count":2}
catalog
{"TimeStamp":"2024-04-17 15:30:44 \u002B0000 UTC","Type":"Warning","ContainerAppName":"catalog","RevisionName":"catalog--vpy9024","ReplicaName":"catalog--vpy9024-57d89dbc74-sbb7x","Msg":"Unable to attach or mount volumes: unmounted volumes=[catalog-aspireshopapphost-catalog-data], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition","Reason":"FailedMount","EventSource":"ContainerAppController","Count":5} {"TimeStamp":"2024-04-17 15:31:56 \u002B0000 UTC","Type":"Warning","ContainerAppName":"catalog","RevisionName":"catalog--vpy9024","ReplicaName":"catalog--vpy9024-57d89dbc74-sbb7x","Msg":"MountVolume.SetUp failed for volume \u0022catalog-aspireshopapphost-catalog-data\u0022 : rpc error: code = Internal desc = volume(csi-d5b2f04ab28a8625a6670b47a31f5ab2adef1a448896482b6f6da67956a6a045) mount //voloplsf5k257d5c.file.core.windows.net/catalog-aspireshopapphost-catalog-data on /var/lib/kubelet/pods/5475d8bd-2b3f-47ca-8fb7-7d9e99e77042/volumes/kubernetes.io~csi/catalog-aspireshopapphost-catalog-data/mount failed with mount failed: exit status 32\nMounting command: mount\nMounting arguments: -t cifs -o ,file_mode=0777,dir_mode=0777,actimeo=30,mfsymlinks,nosharesock,\u003Cmasked\u003E //voloplsf5k257d5c.file.core.windows.net/catalog-aspireshopapphost-catalog-data /var/lib/kubelet/pods/5475d8bd-2b3f-47ca-8fb7-7d9e99e77042/volumes/kubernetes.io~csi/catalog-aspireshopapphost-catalog-data/mount\nOutput: mount error(2): No such file or directory\nRefer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)\n\nPlease refer to http://aka.ms/filemounterror for possible causes and solutions for mount errors.","Reason":"FailedMount","EventSource":"ContainerAppController","Count":10}

Yes this is a known issue https://github.com/dotnet/aspire/issues/3685.

Thanks @davidfowl - made a change on AppHost, and still seeing a similar error.
Here's the edited Program.cs in AppHost. Should we update nuget to preview 4 too?
var builder = DistributedApplication.CreateBuilder(args);

var catalogDb = builder.AddPostgres("catalog", password: builder.CreateStablePassword("catalog-password"));
if (builder.ExecutionContext.IsRunMode)
{
    catalogDb.WithDataVolume();
}

var postgres = catalogDb.AddDatabase("catalogdb");

var basketCache = builder.AddRedis("basketcache")
    .WithRedisCommander();

if (builder.ExecutionContext.IsRunMode)
{
    basketCache.WithDataVolume();
}

var catalogService = builder.AddProject<Projects.AspireShop_CatalogService>("catalogservice")
    .WithReference(postgres);

var basketService = builder.AddProject<Projects.AspireShop_BasketService>("basketservice")
    .WithReference(basketCache);

builder.AddProject<Projects.AspireShop_Frontend>("frontend")
    .WithReference(basketService)
    .WithReference(catalogService)
    .WithExternalHttpEndpoints();

builder.AddProject<AspireShop_CatalogDbManager>("catalogdbmanager")
    .WithReference(postgres);

Should we update nuget to preview 4 too?

Everything has to be updated to preview 5.

Yes I didn't make that change, kept it as preview 5, but still getting the same errors.
Might be going down the bicep edit route...?
Thanks for the super quick response!

Try deploying to a new environment. If you are seeing the same error then something else is wrong.

Yep, re-inited and redeployed to a new environment.  Will take a look again later.

All fixed. Thanks @davidfowl!
Added Projects on this line of code.
builder.AddProject<Projects.AspireShop_CatalogDbManager>("catalogdbmanager")
    .WithReference(postgres);

authors: davidfowl vicperdana

repo: dotnet/aspire-samples


text:
Change how resources expose urls to the dashboard

The resource server used to have a services and endpoints split, that is now a single object called a url which has a name, a full url (uri format) and a bool for if that endpoint is internal (or an implementation detail). Internal urls only show up in the details pane.
Clean up the way we extract urls from the dcp information by mapping the app model resource and endpoint within each service resource in DCP.
Updated tests

Fixes https://github.com/dotnet/aspire/issues/3078
Microsoft Reviewers: Open in CodeFlow

I got an error when I ran TestShop on this branch:
System.Net.Http.HttpRequestException: No such host is known. (catalogservice:443)
 ---> System.Net.Sockets.SocketException (11001): No such host is known.
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
   at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|285_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(QueueItem queueItem)
   at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.HttpConnectionWaiter`1.WaitForConnectionWithTelemetryAsync(HttpRequestMessage request, HttpConnectionPool pool, Boolean async, CancellationToken requestCancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.DiagnosticsHandler.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at Microsoft.Extensions.Http.Logging.LoggingHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
   at Microsoft.Extensions.ServiceDiscovery.Http.ResolvingHttpDelegatingHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) in C:\Development\Source\aspire\src\Microsoft.Extensions.ServiceDiscovery\Http\ResolvingHttpDelegatingHandler.cs:line 59
   at Microsoft.Extensions.Http.Resilience.ResilienceHandler.<>c.<<SendAsync>b__3_0>d.MoveNext()
--- End of stack trace from previous location ---
   at Polly.Outcome`1.ThrowIfException()
   at Microsoft.Extensions.Http.Resilience.ResilienceHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at Microsoft.Extensions.Http.Logging.LoggingScopeHttpMessageHandler.<SendCoreAsync>g__Core|5_0(HttpRequestMessage request, Boolean useAsync, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   at System.Net.Http.Json.HttpClientJsonExtensions.<FromJsonAsyncCore>g__Core|12_0[TValue,TJsonOptions](HttpClient client, Task`1 responseTask, Boolean usingResponseHeadersRead, CancellationTokenSource linkedCTS, Func`4 deserializeMethod, TJsonOptions jsonOptions, CancellationToken cancellationToken)
   at MyFrontend.Components.Pages.Home.OnInitializedAsync() in C:\Development\Source\aspire\playground\TestShop\MyFrontend\Components\Pages\Home.razor:line 77
   at Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync()
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.<WaitForQuiescence>g__ProcessAsynchronousWork|54_0()
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.WaitForQuiescence()
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.RenderRootComponentAsync(Int32 componentId, ParameterView initialParameters)
   at Microsoft.AspNetCore.Components.Endpoints.EndpointHtmlRenderer.SendStreamingUpdatesAsync(HttpContext httpContext, Task untilTaskCompleted, TextWriter writer)

authors: JamesNK davidfowl

repo: dotnet/aspire


text:
COPY failed: CreateFile \?\C:\ProgramData\Docker\tmp\docker-builder564185280\myMicroservice.csproj: The system cannot find the file specified.

Problem encountered on https://dotnet.microsoft.com/learn/aspnet/microservice-tutorial/docker-image
Operating System: windows
Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.
PS C:\Users\mveerabhadra\source\repos\dockerAspCoreDemo> docker build -t mymicroserviceimage .
Sending build context to Docker daemon  1.163MB
Step 1/10 : FROM mcr.microsoft.com/dotnet/core/sdk:2.2 AS build
---> 89ff00e52591
Step 2/10 : WORKDIR /src
---> Using cache
---> 157f0af6de03
Step 3/10 : COPY myMicroservice.csproj .
COPY failed: CreateFile \?\C:\ProgramData\Docker\tmp\docker-builder564185280\myMicroservice.csproj: The system cannot find the file specified.

@madhusudhan-v - what is the name of your csproj file?  Where is it located?  Given the path you included in the description C:\Users\mveerabhadra\source\repos\dockerAspCoreDemo, it appears that you deviated from the tutorial.  That is fine, but you will need to update your Dockerfile accordingly.  Specifically the project name in the COPY and ENTRYPOINT instructions will need to be updated.

Closing stale issue; feel free to re-open if you have more details.

You need to remove existing dockerfile and add new one using visual studio-->right click project->add new-> docker support.
There is a problem in project path defined in dockerfile.

Answer is just move the Dockerfile to where your .sln project is, which your .dockerignore is also located.

authors: MichaelSimons jhunexjun madhusudhan-v mohan023 scalablecory

repo: dotnet/core


text:
SDK Download Archive Links Identical for 1.0.4 and 1.1.1

The SDK download links for .NET Core 1.0.4 and .NET Core 1.1.1 are identical:
https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.0.4-download.md
https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.1.1-download.md
Links from both of the pages point to .NET Core 1.1.1.
Am I missing something? Is there some way how to download SDK installer for .NET Core 1.0.4?

I believe there is just one SDK installer and you get 1.0.4 and 1.1.1 runtimes in it. There is something going on with the naming of the sdk file though.
@livarcocc , Is the filename of the RTM SDK that is branded as 1.0.1 actually 1.1.1?

Ok, thanks for the explanation.
Are there any download links for tooling for VS2015 or is it all VS2017-only now? I unfortunately cannot update to VS2017 at the moment.
I cannot get VS2015 to work with a .NET Core project based on project.json (even a brand new project from a VS template), I always get this:

Tried uninstalling everything and installing the SDKs from the links above, so now I am looking for older versions, because I remember this used to work.

All the updates are VS 2017 and a lot of improvements were made there. I'm not familiar with that error.

I assume that there were significant changes that are breaking to VS 2015.
There should be a help page that specifies how to lock your project back to the preview2 tooling. Where is that @blackdwarf @mairaw ?

@richlander Yeah, you're right, it seems that it's the preview2 tooling that I'm looking for (AFAIK the move from project.json to msbuild was in preview3). Is it still possible to get it somewhere?

Is it still possible to get it somewhere?

Sorry, I'm slow. What does "it" refer to?

I believe @tompazourek means the Preview 2 bits. The whole archive is @ https://github.com/dotnet/core/tree/master/release-notes/download-archives.

@blackdwarf What about the installers that contain the MSBuild DotNet Core targets and props files for Visual Studio 2015? I can't seem to find anything that installs those files.

@daschult - There isn't such a configuration. We didn't enable the msbuild tools to work with .NET Core. This is documented here: https://blogs.msdn.microsoft.com/dotnet/2017/03/07/announcing-net-core-tools-1-0/

authors: Petermarcu blackdwarf daschult richlander tompazourek


text:
Update ANCM versions

Propagate changes from https://github.com/dotnet/dotnet-core-website/pull/830/

We are carrying these edits for the big push on 12/4 so we can probably skip this PR

authors: shirhatti vivmishra


text:
Fix arguments with = before :

Fixes #1164
This fixes the issue where ':' was preferred as the option/argument separator even when there was a '=' earlier in the string.

@dotnet-bot test Windows Release please

looks good

authors: KrzysztofCwalina alexperovich

repo: dotnet/corefxlab

license: mit

license_source: bigquery


text:
Remove "new NotImplementedExceptions" from IO code.

Sites found by tooling:
[System.Private.CoreLib] System.IO.Stream.SyncStream::BeginRead(byte[], int, int, AsyncCallback, object)
[System.Private.CoreLib] System.IO.Stream.SyncStream::BeginWrite(byte[], int, int, AsyncCallback, object)

How to remove:

Include the following in your .csproj file:

    <Compile Include="..\..\Common\src\System\NotImplemented.cs">
      <Link>System\NotImplemented.cs</Link>
    </Compile>

Options for removing “throw new NotImplementedException()”:
If you can implement the missing functionality now:
Do so.
If this is functionality that’s not supported on a particular framework or OS, replace with
throw new PlatformNotSupportedException(SR.xxx);
If this is an api that needs to throw NotImplemented for backward compat reasons, replace with:
throw NotImplemented.ByDesign;
or
throw NotImplemented.ByDesignWithMessage(SR.xxx);
If this is a virtual api method that’s only intended to work when overridden by another class, replace with:
throw new NotSupportedException(SR.xxx);
(Unless required for backward compat, refrain from throwing NotImplemented out of these.)
If this is a virtual non-api method that’s only intended to work when overridden by another class, replace with:
An abstract method.
If this is a compiler or toolchain intrinsic that only needs a body to make C# happy:
throw new NotSupportedException();
If this is true undone work and you just can’t fix it now, replace with:
throw NotImplemented.ActiveIssue(“https://github.com/dotnet/corert/issues/xxx”);
The string will not leak out via Exception.Message. The string is for tooling and human readers only. In the past, we’ve usually added an inline comment but the trouble with those is that IL-based tooling can’t read comments.

Now tracked as TFS 451317

repo: dotnet/corert


text:
Add support for ExplicitScopeAttribute to metadata generation

Add new IMetadataPolicy member to control the defining module of a type
Added mixin implementation that works for ExplicitScopeAttribute
Added WinRT explicit scope defined types in both the primary metadata assembly and same metadata assembly
Added single file and multi file tests to ensure that both definition and reference to these relocated types is correct

LGTM. Thanks!

authors: MichalStrehovsky davidwrighton


text:
Pass RID to crossgen

Based on https://github.com/dotnet/buildtools/issues/2050
Contributes to https://github.com/dotnet/corert/issues/5857
cc @weshaggard, @dagood; please note that https://github.com/dotnet/corert/issues/5962 is an existing problem, PR shall not regress from the baseline :)

It looks like that this fixing the crossgen.sh: line 80: $2: unbound variable errror https://github.com/dotnet/corefx/issues/30043 ? If yes, could you please make the same fix in CoreCLR/FX as well?

@jkotas, yes. The second argument was made optional in https://github.com/dotnet/buildtools/pull/2061, so the latest build tools will not break. However, it would be great if all repos start passing this argument as crossgen throws non-fatal errors on Alpine and continues. I will prepare the PRs.


text:
Wasm: Change boolean logic for gc.cpp find_object

This PR implements the suggestion in #8205.  I'm submitting the PR as with this change and #8171 its possible to run 100 iterations of the Generics test without a memory access failure.
Fixes #8210
Closes #8205
Draft as depends on #8171

Would you mind submitting the gc.cpp change to dotnet/runtime ?

Closing as replaced by https://github.com/dotnet/runtime/pull/39905

authors: jkotas yowl


text:
WinForms designer copy/paste changed from .NET Framework

https://github.com/microsoft/winforms-designer/issues/5251
Copy and pasting controls from one form to the other doesn't bring along the events, unlike in .NET Framework. After copying, the designer will display errors related to the missing event handlers.

Associated WorkItem - 117822

After further review, there is actually no breaking change here and nothing to document

repo: dotnet/docs-desktop


text:
Troubleshoot 32-bit errors

Summary
Outstanding questions:

Which version of Visual Studio 2022 is required?
Is it still the <UseWinFormsOutOfProcDesigner>True</UseWinFormsOutOfProcDesigner> setting still valid?
Do you need to turn on the auto detection feature in Visual Studio's settings?

Fixes #1750

Internal previews

📄 File
🔗 Preview link

dotnet-desktop-guide/net/winforms/visualstudio/troubleshoot-32bit.md
dotnet-desktop-guide/net/winforms/visualstudio/troubleshoot-32bit

@tdykstra

My general issue with it is this:
I think the problem is not so much if your WinForms App is 32-Bit or 64-Bit, it is rather if it relies of a 32-Bit component which can only run in a 32-Bit process. BTW: the same applies for the other way around with 64-Bit and VS 2019. It would not have been possible to run an app in the VS 2019 32-Bit bound designer, which was definitely not the case. So, we compile the assembly relevant for showing design-time-functionality in VS 2022 in 64-Bit and in VS 2019 in 32-Bit, no matter what your project's actual bitness is. Only if there is a component, which doesn't work in 32-Bit in VS 2019, or in 64-Bit in VS 2022, we run into problems. The first case almost never happens, but now, with VS 2022, the reversed case does.
@Shyam-Gupta is a better candidate to confirm and do a detailed review of this - he also wrote the respective blog post.

Which version of Visual Studio 2022 is required?
17.9 Preview 2 or newer
Is it still the True setting still valid?
Yes
Do you need to turn on the auto detection feature in Visual Studio's settings?
This feature is ON by default. It is controlled by following option in VS -> Tools -> Options -> Preview Features:

authors: KlausLoeffelmann Shyam-Gupta adegeo


text:
Add missing letter in first link of article

Summary
Adds missing letter to the first link of the document.
Fixes #66

@ignispotentia ACK! I just noticed this was pointing to the LIVE branch, this should be the MASTER branch. I'll revert this. 😿

Didn't want to change anything, so I just took the default values that Github gave me when I edited 😂 it's probably my fault also a little bit.

HRM yes I'll have to check that, it should have (in the issue opened) pointed to master.

No worries, glad we found it out in time 😁

Awesome. Found the config to adjust that so future comments appear to target the correct branch 😄  #70 thanks for forcing me to uncover that error hahaha.

Awesome! And haha, considering the number of times MSDN docs helped me, this is the least I could do

authors: adegeo ignispotentia


text:
Publish as self-contained app "side-by-side"

Is it possible to use the command dotnet publish -r win10-x64 on the same csproj file used to generate a tool?
Use case: I would like to generate both an executable and the dotnet tool.
If I try, I get the following error: * error NETSDK1053: Pack as tool does not support self contained.*
I tried it with SDK versions 2.2.106 and 2.2.203

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6ffe064a-2c6e-284f-7706-528d1c861de3
Version Independent ID: 7ff2fe61-8884-694d-db38-3e2cc292fe61
Content: How to create a .NET Core Global Tool - .NET Core CLI
Content Source: docs/core/tools/global-tools-how-to-create.md
Product: dotnet-core
Technology: dotnet-cli
GitHub Login: @Thraka
Microsoft Alias: adegeo

Yes! Just turn off the <PackAsTool> property on the command line 😄
dotnet publish -r win10-x64 /p:PackAsTool=false

I'm going to close this issue. If your problem is not solved, feel free to reopen or comment. Thanks!

authors: Thraka fleed

repo: dotnet/docs


text:
code formatting issue

There is one formatting issue in docs How to: Parse Strings Using String.Split.
string[] separatingChars = { "<<", "..." };
    string text = "one<<two......three<four";
    System.Console.WriteLine("Original text: '{0}'", text);

    string[] words = text.Split(separatingChars, System.StringSplitOptions.RemoveEmptyEntries );
    System.Console.WriteLine("{0} substrings in text:", words.Length);

    foreach (var word in words)
    {
        System.Console.WriteLine(word);
    }

Should be like this
string text = "one<<two......three<four";
System.Console.WriteLine("Original text: '{0}'", text);
string[] words = text.Split(separatingChars, System.StringSplitOptions.RemoveEmptyEntries );
System.Console.WriteLine("{0} substrings in text:", words.Length);
foreach (var word in words)
{
System.Console.WriteLine(word);
}
This code should be in the same format as the previous two pieces of code. There should be no spaces before each line of code.

Thanks for your feedback @jack147527. This was fixed in https://github.com/dotnet/samples/pull/847.


text:
VB.NET is incorrectly omitted

The documentation fails to mention that *.vbproj files are supported as well.
https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-pack#arguments

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a7e805a3-f2ec-b05a-d5c8-29f7a8c16a5f
Version Independent ID: 4257ec12-df6f-ec52-aad3-012e5fce8133
Content: dotnet pack command - .NET Core CLI
Content Source: docs/core/tools/dotnet-pack.md
Product: dotnet-core
Technology: dotnet-cli
GitHub Login: @tdykstra
Microsoft Alias: tdykstra

Easy enough to fix, but before that, I'll wait someone to confirm if only vbproj is missing, or fsproj is missing too.
cc: @cartermp Can you confirm if dotnet pack works for fsproj files or not?

Yes, dotnet pack works for all project files (csproj, vbproj, fsproj)

@cartermp, Thanks. Opened #18446

authors: InteXX Youssef1313 cartermp


text:
System.IO APIs throw exceptions for invalid paths only when used, not when normalizing

System.IO APIs throw exceptions for invalid paths only when used, not when normalizing
See https://docs.microsoft.com/en-us/archive/blogs/jeremykuhne/system-io-in-net-core-2-1-sneak-peek
See https://github.com/dotnet/runtime/issues/38487#issuecomment-650665737
I'll let a product team member writes this in a more organized way.
Version introduced
.NET Core 2.1
Old behavior
System.IO APIs used to throw exceptions for invalid paths when normalizing a path.
New behavior
System.IO APIs are no longer throwing exceptions when normalizing a path. They only throw exceptions when using the path.
Reason for change
Leaving this to the product team to write.
Recommended action
Leaving this to the product team to write.
Category

Core .NET libraries

Affected APIs
I don't have a complete list of the affected APIs.
Note
The API reference (for example, for FileInfo ctor) is outdated. It states that it will throw an exception for invalid paths.

Issue metadata

Issue type: breaking-change

@gewarren, Do you know who can give more information on this?

@carlossanlop and @Jozkee are listed as the owners.

This is by design. If the user wants to manipulate made up paths, they should be able to. But once you make a call to the OS, that's when the exception should be thrown, since the path did not exist.
This is explained in Jeremy Kuhne's blog when the feature was announced:

Exceptions for "bad" paths are thrown when used, not when normalizing (as we can't know what is "valid" without using them)

Exceptions for "bad" paths are thrown when used, not when normalizing (as we can't know what is "valid" without using them)

@carlossanlop It might be by design, but it seems like we should document it as a breaking change?

@carlossanlop, This issue is about missing documentation for the breaking change, and outdated API reference.

@gewarren Can you please re-open so this doesn't get missed?
Pinging @carlossanlop @Jozkee

@carlossanlop It might be by design, but it seems like we should document it as a breaking change?

Yes, we need to document the breaking change, @gewarren.
We should also edit the documentation of Path APIs that have an exception when detecting invalid chars, and make sure to indicate they only throw in .NET Framework.

authors: Youssef1313 carlossanlop gewarren


text:
Update Prerequisites topics for .NET Core 2.2

[ ] Windows: https://docs.microsoft.com/en-us/dotnet/core/windows-prerequisites
[x] macOS: https://docs.microsoft.com/en-us/dotnet/core/macos-prerequisites
[x] Linux: https://docs.microsoft.com/en-us/dotnet/core/linux-prerequisites

Following up with author of https://github.com/dotnet/core/blob/master/release-notes/2.2/2.2-supported-os.md to confirm there are no changes to prereqs for 2.2

I just checked the Windows version and is not fully up-to-date. I'll create a PR shortly with some more changes to address this. I'll check the others later.

@Andrew-MSFT @KathleenDollard @richlander I don't seem to be able to select the Target Framework version from the Build menu on VS 15.9.3 anymore. By design?

I'm updating the screenshots we have at https://docs.microsoft.com/en-us/dotnet/core/windows-prerequisites#prerequisites-with-visual-studio-2017.

@davkean and @cartermp.  Not by design, mine looks like that but if I click the dropdown I can see the frameworks.  Is yours clickable?

Mine doesn't look like that with File | New Project. Is this for an existing project?

In my case, yes it was an existing project

Yes, existing project for me as well, but not clickable in my case.

A new project works fine 😕

And 15.9 comes with 2.1 SDK by defaut, correct?

Never mind. It seems there was something funky going on with my machine and that particular project. The drop-down now shows fine for that one as well.
So if I can just get confirmation that 2.1 SDK comes with the 15.9, I'll finish the updates I'm working on.
Thanks!

The 2.1 SDK does come with 15.9, yes.

Thanks @cartermp.

authors: Andrew-MSFT Thraka cartermp mairaw


text:
Update Unit Testing with XUnit

Fixes #1468

Closing as this targeted the wrong branch. The same changes have been re-opened in PR #1537 against the master branch.

Ignore previous comments. These changes should target the csproj branch. Re-opening and closing #1537

closing and reopening to start a build.


text:
[WIP] F# 4.5

Intentionally leaving out span work, as @TIHan will be covering that.

Closing as I apparently deleted my clone and that borked this whole thing up


text:
Run collection rule action tests serially

Summary
This change runs the collection action tests serially so that they do not apply thread pool pressure to each other. The PassThrough action has also been rewritten to avoid using the CollectionRuleActionBase class, which is susceptible to delayed execution when the thread pool is starved.

Release Notes Entry

/backport to release/7.x

repo: dotnet/dotnet-monitor


text:
Label needs-author-action is not getting automatically applied/removed in machinelearning

As observed in https://github.com/dotnet/machinelearning/issues/6098, the needs-author-action label should have been automatically removed when the author commented, but the label was not automatically removed.
This is caused by not having the same set of tasks in the machinelearning repo that we have in the runtime repo. Specifically, the runtime repo has the following tasks related to the needs-author-action label:

Replace needs-author-action label with needs-further-triage label when the author comments on an issue
Add no-recent-activity label to PRs
Needs-author-action notification
PR reviews with "changes requested" applies the needs-author-action label
Pushing changes to PR branch removes the needs-author-action label
Author commenting in PR removes the needs-author-action label
Author responding to a pull request review comment removes the needs-author-action label

At present, we don't have those tasks as part of the generated configuration tasks. We need to decide if those tasks should be generated from the scripts in this repository or if we should just have them replicated in each of the repos where that behavior is desired.
/cc @michaelgsharp

There are other tasks directly configured in the runtime repo that aren't configured in the machinelearning repo either. Another example is Assign Team PRs to author. We should review all of the non-area-pod tasks in the runtime repo to see which others we want to apply to the machinelearning repo and which we want to standardize through the scripts in fabricbot-config.

repo: dotnet/fabricbot-config


text:
Adding a change log

I have noticed that sometimes we are getting updates to ML.NET Model Builder with no changelogs (or at least I haven't seen them). Since this project is (still?) not open source, it's impossible for us to figure out what changed.
Can we have one consistent place for changes and have a link to that from:

https://marketplace.visualstudio.com/items?itemName=MLNET.07
https://docs.microsoft.com/en-us/dotnet/machine-learning/automate-training-with-model-builder

Alternatively, you can publish the extension as open-source and off-load the work to the community. 😉

@jernejk, thanks for your recommendation to make ML.Net Model Builder open source !
@JakeRadMSFT, what is the plan around to make it open source?

@jernejk, thanks for your recommendation to make ML.Net Model Builder open source !
@JakeRadMSFT, what is the plan around to make it open source?

Thanks @jernejk! We'll start adding change logs! That's a great idea!
No ETA on Open Sourcing yet but we have been preparing to do so!

Thanks @jernejk! We'll start adding change logs! That's a great idea!
No ETA on Open Sourcing yet but we have been preparing to do so!

Thanks. :)
I'm frequently doing demos to clients and audiences on various events, and it's nice to know what changed. 😊
I have once done a live demo in December where the UI completely changes and half of my demo was "Oh, they fixed that too... Awesome, I can now talk more about X!". 😂 (some of them were scripted as some have already seen my demos)
Great job on Model Builder. 🤗

Thanks. :)
I'm frequently doing demos to clients and audiences on various events, and it's nice to know what changed. 😊
I have once done a live demo in December where the UI completely changes and half of my demo was "Oh, they fixed that too... Awesome, I can now talk more about X!". 😂 (some of them were scripted as some have already seen my demos)
Great job on Model Builder. 🤗

We've started adding change logs! You can see them here - https://github.com/dotnet/machinelearning-modelbuilder/tree/main/docs/release-notes. The first one covered about 9 months of work, so it isn't as detailed as I'd like, but we will improve as our releases becomes more regular.
Thank you for the suggestion @jernejk! Please let us know when you have other ideas or thoughts.

authors: JakeRadMSFT beccamc jernejk zewditu

repo: dotnet/machinelearning-modelbuilder


text:
Removed duplicate Participate method

Removed duplicate Participate method from FileGrainStorage class

Docs Build status updates of commit b02de88:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

src/docs/tutorials_and_samples/custom_grain_storage.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

authors: bradygaster staviloglu

repo: dotnet/orleans-docs


text:
F12 support for class libraries outside of the project

Direct customer ask copying here:

Another feature I would like is to be able to press F12 when the caret is over a Razor component to navigate to the implementation, just like you can for classes.

This appears to be working with VS2022 17.3.6. I was able to use F12 to go to a component defined in a referenced Razor class library.

repo: dotnet/razor-tooling


text:
[WebToolsE2E] Error list has no warnings when add some code in Layout.cshtml

Backing VSTS issue: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1361463

This is no longer an issue, was fixed by our "inferred" diagnostic support


text:
Cannot properly run razor tooling as a VS extension when building from source

I faced a problem when trying to build razor tooling code and run it as a VS Extension. The build was done according to this instruction: https://github.com/dotnet/razor-tooling/blob/main/docs/contributing/BuildFromSource.md, "Building in Visual Studio". All is built ok, but when I try to run this, I get an unhandled exception:

File: Microsoft.VisualStudio.RazorExtension.RazorPackage. Message:

Export pending (1) with contract name "Microsoft.VisualStudio.LanguageServerClient.Razor.Debugging.RazorBreakpointResolver", but after applying restrictions found 0.

Message was translated from different language by myself
Stack trace:
at Microsoft.VisualStudio.Composition.ExportProvider.GetExports(ImportDefinition importDefinition)
at Microsoft.VisualStudio.Composition.ExportProvider.GetExports[T,TMetadataView](String contractName, ImportCardinality cardinality)
at Microsoft.VisualStudio.Composition.ExportProvider.GetExport[T,TMetadataView](String contractName)
at Microsoft.VisualStudio.Composition.ExportProvider.GetExportedValue[T]()
at Microsoft.VisualStudio.ComponentModelHost.ComponentModel.GetService[T]()
at Microsoft.VisualStudio.RazorExtension.RazorPackage.<>c.<InitializeAsync>b__1_0(IServiceContainer container, Type type) в <Path to razor-tooling project folder>\src\Razor\src\Microsoft.VisualStudio.RazorExtension\RazorPackage.cs:line 47
at Microsoft.VisualStudio.Shell.Package.GetService(Type serviceType)
at Microsoft.VisualStudio.Shell.AsyncPackage.GetService(Type serviceType)
at Microsoft.VisualStudio.Shell.Package.InternalQueryService(Guid& sid, Guid& iid, IntPtr& ppvObj)
at Microsoft.VisualStudio.Shell.AsyncPackage.InternalQueryService(Guid& sid, Guid& iid, IntPtr& ppvObj)

After launching another VS with extension inside, it does not work properly. At least syntax colorization is weird:

This is an App.razor file from one of my projects. As you see, all razor components are colorozed as html tags, C# syntax colorization
in a @code block is partial as well.
Visual Studio Community 2022 v17.0.4
Node.js v17.3.0
Yarn v1.22.17
Python v3.10.1
No idea how to deal with it. Please help.

Just cheked VS 2022 v17.1 Preview 1.1 and situation there is almost the same. The same exception is thrown and almost the same result when trying to open a razor file. Several more exceptions are thrown when you open and close document, but this is the result of the first exception, I think.

@DoctorKrolic that's super odd! Hmmm, I wonder if your experimental hive is broken possibly? Would you mind going to your %localappdata%\Microsoft\VisualStudio folder and deleting any folder in there that has RoslynDev as a suffix and then re-trying? That's Visual Studio's temporary "hive" that allows extensions to run along side of normal VS development

@NTaylorMullen It didn't help( I also tried to reinstall VS from scratch, it didn't help as well

@DoctorKrolic quite interesting... If you open up your equivalent of "C:\Users\nimullen\AppData\Local\Microsoft\VisualStudio\17.0_9b8618ceRoslynDev\ComponentModelCache\Microsoft.VisualStudio.Default.err" do you ese any errors in that file in association with Razor?

Microsoft.VisualStudio.Default.err
A bunch of exceptions, mostly "Something went wrong because of FileNotFoundException"

Oh geez, look at that, I didn't even realize we had bumped our Roslyn version to 4.1.0 (in that log it shows failure to load those pieces). If you'd like you can checkout our release/17.0.2 branch which should work with latest 17.0 builds. Once 17.1-P2 is released I believe you should be able to use latest VSMain branch on that.

Tried VS 2022 v17.1 Preview 2 and all works fine. Closing the issue

authors: DoctorKrolic NTaylorMullen


text:
Investigate TagHelper scanning improvements

Today, we need to scan all referenced assemblies to determine whether each assembly has defined any tag helpers. This is pretty inefficient, and pretty wasteful: most assemblies users reference couldn't have defined any tag helpers, since they don't reference Microsoft.AspNetCore.Razor.dll. Further, even among the assemblies that could have, many won't, so we're wasting a large amount of time looking for tag helpers where none exist. To address this, I'd like to propose the following scanning algorithm for .NET 9:

Does the assembly reference Microsoft.AspNetCore.Razor.dll?

If it does, is the version >8? If so, look for an attribute on the module, something like Microsoft.AspNetCore.Razor.ContainsTagHelpers. If that attribute is present, the assembly contains tag helpers and should be searched. Otherwise, it does not contain tag helpers and can be skipped.
If it does, and the version is <=8, scan the assembly. We have no information on whether tag helpers are actually present.

If it does not, there cannot be any tag helpers. Don't scan the assembly.

This will require putting a new source generator into the ref packages for Microsoft.AspNetCore.Razor so that anyone that defines tag helpers will get a module attribute automatically. This pattern is inspired by how C# does extension method lookups.

An alternative strategy for the 1.1 and 1.2 subbullets would be to have ContainsTagHelpers take a bool: if the attribute is present, we will then always know whether we need to scan. If the attribute is not present, we always need to scan. The main cost here would be slight assembly size bloat for assemblies that do not define any tag helpers.

repo: dotnet/razor


text:
Upgrade RuntimeInformation from 4.0 -> 4.3

This is to prevent a downgrade error when running on a machine with https://github.com/dotnet/sdk/pull/893.
Filed https://github.com/NuGet/Home/issues/4703 to track the large number of warnings/errors this case caused.

tag @dotnet/project-system @BillHiebert

repo: dotnet/roslyn-project-system


text:
Fix the COM sample to work on latest preview

The COM server sample was written for .NET Core 3.0 Preview 5. Since then the way the COM hosting is setup changed slightly so the sample doesn't work on latest previews.
The change fixes it to work on preview 8 (and breaks it on earlier previews).
Also some small tweaks to the readme.

@elinor-fung I thought you fixed this?

#1064 - we were waiting for Preview 7 to actually be released to merge.

Completely missed #1064 - closing this as it's a duplicate.

repo: dotnet/samples


text:
remove snippet tag

The snippet tags are being rendered on the docs and are not really needed
https://docs.microsoft.com/en-us/dotnet/visual-basic/programming-guide/language-features/procedures/ref-return-values
I'm wondering if the addition of the BOM marks in PR #1091 broke the logic to remove the snippet tags. Maybe if the snippet tag is in the first line, it doesn't behave as expected?

No clue. 😉


text:
Support for Azure Trusted Signing

With Azure Trusted Signing (formerly Azure Code Signing) now in public preview it would be handy to be able to sign files/clickonce using the Trusted Signing service.
Some more links:

https://www.powershellgallery.com/packages/TrustedSigning

Would love to see support for this. The @ImageMagick project has a Trusted Signing certificate and we are using this to sign our installers and executables. But there is no support for that in this tool yet. And I would like to also sign my ImageMagick NuGet packages using that certificate in a GitHub pipeline.

Throwing my weight behind this as I have a new package I want to test with and I'm trying to keep everything in GitHub actions ad an added bonus.

I am also supporting this request, our developers need to migrate to trusted signing, but without support for clickonce in any of the other trusted signing tools, that is not possible.

This integration should probably use the SDK https://www.nuget.org/packages/Microsoft.Trusted.Signing.Client
Do take care that the SDK linked in trusted signing docs is deprecated

@ROGG437063 sorry for the confusion on the docs regarding the SDK. We have kept the current version from our preview unlisted while we prep a new release of the SDK. This SDK will become publicly listed in the very near future. https://www.nuget.org/packages/Azure.CodeSigning.Sdk
cc: @Jaxelr

@ROGG437063  Indeed, we expect the SDK to be publicly available once we sort through a few issues on the PR, but you can track that work here: https://github.com/Azure/azure-sdk-for-net/pull/41191

@Jaxelr Sounds good, any estimate of when that will be merged? It would also still need integration with sign cli for vsto manifest signing, right?

Must to have. Please push 🙌🏻

This prerelease version has Trusted Signing support.  Thanks to @dlemstra for adding it!  👏

This prerelease version has Trusted Signing support. Thanks to @dlemstra for adding it! 👏

This works great!

authors: EuanKerr Jaxelr ROGG437063 blowdart demiliani dlemstra dtivel ianjmcm mjcheetham

repo: dotnet/sign


text:
Initial port from service to CLI

The CLI is in rough shape:  very little in the way of argument validation and actionable feedback.  You're more likely to get an exception than a friendly error at this point.  I will handle this in a subsequent PR.
I verified that, when passed the right arguments, the CLI does Authenticode sign a binary successfully.  I have not yet verified other scenarios.
This builds and unit tests run successfully.  Note that dotnet restore bootstrap.proj is a currently manual build prestep.
CC @clairernovotny

@clairernovotny, fixed console logging not displaying and simplified tools copying.


text:
Support latest C# versions

When using the .Net Editor on the Microsoft site it is not supporting the latest version of C#, I tried to do a challenge with the switch expression and pattern matching and it doesn't recognise either.
Update to support the latest language features.

Strongly needed. I need to demonstrate simple C# code online to show others the power of C#.

Done.

authors: dimohy gordug jonsequitur

repo: dotnet/try


text:
Github Actions Tye push

I better start by saying i'm still learning github actions and this could be my innability to configure the yaml.
I have an API in .net 6 and i'm trying to use Actions CI to do "tye push tye.yaml". (tye latest version "0.2.0-alpha.20258.3"). It works fine locally.
This is the push part of my pipeline:
deploy:
    needs: build
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2
    - name: Setup .NET Core 3.1
      uses: actions/setup-dotnet@v1
      with:
        dotnet-version: '3.1'
    - name: Setup .NET
      uses: actions/setup-dotnet@v1
      with:
        dotnet-version: '6.0'
        include-prerelease: True
    - name: Install tye
      run: dotnet tool install -g Microsoft.Tye --version "0.2.0-alpha.20258.3"
    - name: List Runtimes
      run: dotnet --list-runtimes
    - name: Push to DockerHub
      run: tye push tye.yaml

Here's the output:
Run tye push tye.yaml
  tye push tye.yaml
  shell: /usr/bin/bash -e {0}
  env:
    DOTNET_ROOT: /home/runner/.dotnet
Loading Application Details...
An unhandled exception has occurred, how unseemly:
System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.

File name: 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
   at Microsoft.Tye.ProjectReader.EvaluateProject(OutputContext output, ProjectServiceBuilder project)
   at Microsoft.Tye.ProjectReader.ReadProjectDetailsAsync(OutputContext output, ProjectServiceBuilder project) in /_/src/Microsoft.Tye.Core/ProjectReader.cs:line 80
   at Microsoft.Tye.ApplicationFactory.CreateAsync(OutputContext output, FileInfo source) in /_/src/Microsoft.Tye.Core/ApplicationFactory.cs:line 99

The version of Tye you are using 0.2.0-alpha.20258.3 does not support .NET 6. Therefore you should switch to .NET 5 and especially update the Tye version.

Thank you. Didn't realise i was using 0.10 locally and 0.2 in the pipeline. Stupid mistake xD

authors: SpeedySDK samtrion

repo: dotnet/tye


text:
'docker build'-step of tye deploy fails when project is not on system drive

Describe the bug
The 'tye deploy' command fails when the project is not on the system drive. The 'docker build' step results in an error.
To Reproduce
Create and deploy a solution on a drive other than the system drive:
dotnet new razor -n frontend
dotnet new sln
dotnet sln add frontend
tye deploy --interactive

This results in the following error:

These steps work on the system drive and fail on any other.
Further technical details

Version: 0.1.0-alpha.20168.8+f45b9444d4894009bde48e2a3411a52dd09497b1
Windows 10 1909
Docker Desktop 2.2.0.4

Thanks for the report! We'll fix this.

This should be fixed as of 0.1.0-alpha.20174.3 - I don't have easy access to a windows machine to test it right now, so please let us know if you hit issues.

The build still fails with the same error:

Ok, I'll take a look at this again.

@SebastianLng -  I cannot reproduce this failure. I suspect I may have told you the wrong version for the fix 😢
The fix was to publish to a temp folder instead of inside the app's folder. Relevant bit from the logs (which I don't see in your example)
Running 'dotnet publish'.
        > dotnet publish "D:\testing\testing.csproj" -c Release -o "C:\Users\rynowak.REDMOND\AppData\Local\Temp\pyaopkfm.cmx"
            Microsoft (R) Build Engine version 16.5.0+d4cbfca49 for .NET Core
            Copyright (C) Microsoft Corporation. All rights reserved.

              Restore completed in 33.83 ms for D:\testing\testing.csproj.
              You are using a preview version of .NET Core. See: https://aka.ms/dotnet-core-preview
              testing -> D:\testing\bin\Release\netcoreapp3.1\testing.dll
              testing -> C:\Users\rynowak.REDMOND\AppData\Local\Temp\pyaopkfm.cmx\
        Done running 'dotnet publish' exit code: 0
        Created Publish Output: 'Microsoft.Tye.TempDirectory'

If you're still seeing this can you pass -v debug and include the output?
Here's what I get using tye build -v debug (this does the container build step).
> tye --version
0.1.0-alpha.20208.4+3f994be2fd4b9acaebb69a896141e154ffe9ae36

Locating .NET SDK...
Found .NET SDK at: C:\Program Files\dotnet\sdk\3.1.200-preview-015002\
Registered .NET SDK.Loading project 'D:\testing\testing.csproj'.
Loaded project 'D:\testing\testing.csproj'.
Build started 4/8/2020 5:56:21 PM.
__________________________________________________
Project "D:\testing\testing.csproj" (Restore;ResolveReferences;ResolvePackageDependenciesDesignTime;PrepareResources;GetAssemblyAttributes target(s)):

Target _FilterRestoreGraphProjectInputItems:
    __________________________________________________
    Project "D:\testing\testing.csproj" is building "D:\testing\testing.csproj" (_IsProjectRestoreSupported target(s)):

Target _GetAllRestoreProjectPathItems:
    __________________________________________________
    Project "D:\testing\testing.csproj" is building "D:\testing\testing.csproj" (_GenerateRestoreProjectPathWalk target(s)):

    __________________________________________________
    Project "D:\testing\testing.csproj" is building "D:\testing\testing.csproj" (_IsProjectRestoreSupported target(s)):

Target _GenerateRestoreGraph:
    __________________________________________________
    Project "D:\testing\testing.csproj" is building "D:\testing\testing.csproj" (_GenerateRestoreGraphProjectEntry target(s)):

    __________________________________________________
    Project "D:\testing\testing.csproj" is building "D:\testing\testing.csproj" (_GenerateProjectRestoreGraph target(s)):

Target Restore:
    Committing restore...
    Assets file has not changed. Skipping assets file writing. Path: D:\testing\obj\project.assets.json
    Restore completed in 45.23 ms for D:\testing\testing.csproj.

    NuGet Config files used:
        C:\Users\rynowak.REDMOND\AppData\Roaming\NuGet\NuGet.Config
        C:\Program Files (x86)\NuGet\Config\Microsoft.VisualStudio.Offline.config

    Feeds used:
        https://api.nuget.org/v3/index.json
        C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:00:00.65
Found application version: 1.0.0
RunCommand=D:\testing\bin\Debug\netcoreapp3.1\testing.exe
RunArguments=
TargetPath=D:\testing\bin\Debug\netcoreapp3.1\testing.dll
PublishDir=bin\Debug\netcoreapp3.1\publish\
AssemblyName=testing
IntermediateOutputPath=obj\Debug\netcoreapp3.1\
Found target framework: netcoreapp3.1
Found shared frameworks: Microsoft.NETCore.App, Microsoft.AspNetCore.App
IsAspNet=True
Evaluation Took: 945.8777ms
Processing Service 'testing'...
    Compiling Services...
    Done Compiling Services...
    Publishing Project...
        Running 'dotnet publish'.
        > dotnet publish "D:\testing\testing.csproj" -c Release -o "C:\Users\rynowak.REDMOND\AppData\Local\Temp\pyaopkfm.cmx"
            Microsoft (R) Build Engine version 16.5.0+d4cbfca49 for .NET Core
            Copyright (C) Microsoft Corporation. All rights reserved.

              Restore completed in 33.83 ms for D:\testing\testing.csproj.
              You are using a preview version of .NET Core. See: https://aka.ms/dotnet-core-preview
              testing -> D:\testing\bin\Release\netcoreapp3.1\testing.dll
              testing -> C:\Users\rynowak.REDMOND\AppData\Local\Temp\pyaopkfm.cmx\
        Done running 'dotnet publish' exit code: 0
        Created Publish Output: 'Microsoft.Tye.TempDirectory'
    Done Publishing Project...
    Building Docker Image...
        Writing Dockerfile to 'C:\Users\rynowak.REDMOND\AppData\Local\Temp\pyaopkfm.cmx\Dockerfile'.
        Done writing Dockerfile.
        Running 'docker build'.
        > docker build "C:\Users\rynowak.REDMOND\AppData\Local\Temp\pyaopkfm.cmx" -t testing:1.0.0 -f "C:\Users\rynowak.REDMOND\AppData\Local\Temp\pyaopkfm.cmx\Dockerfile"
            Sending build context to Docker daemon  290.8kB

            Step 1/4 : FROM mcr.microsoft.com/dotnet/core/aspnet:3.1
             ---> e2cd20adb129
            Step 2/4 : WORKDIR /app
             ---> Using cache
             ---> 2b4aaeb2d6f3
            Step 3/4 : COPY . /app
             ---> Using cache
             ---> e39a5848b8a1
            Step 4/4 : ENTRYPOINT ["dotnet", "testing.dll"]
             ---> Using cache
             ---> 6f16231dc917
            Successfully built 6f16231dc917
            Successfully tagged testing:1.0.0
            SECURITY WARNING: You are building a Docker image from Windows against a non-Windows Docker host. All files and directories added to build context will have '-rwxr-xr-x' permissions. It is recommended to double check and reset permissions for sensitive files and directories.
        Done running 'docker build' exit code: 0
        Created Docker Image: 'testing:1.0.0'
    Done Building Docker Image...
Done Processing Service 'testing'...

I tried it again with the new release 0.1.0-alpha.20209.5+e3fc0045bd1e5913da935241874761929f1e8465
It works for me now, looks like you did fix it :)

Awesome!

I'm glad it's working for you. Sorry for the confusion. My guess is that I told you the wrong build to try.

I've encountered this issue:
windows 10
c:\temp\ms>tye --version
0.10.0-alpha.21420.1+7cec0655cc474aee8d3c3a3d180678985209d439
c:\temp\ms>tye deploy -i
Loading Application Details...
Verifying kubectl installation...
Verifying kubectl connection to cluster...
Processing Service 'frontend'...
Applying container defaults...
Compiling Services...
Publishing Project...
Building Docker Image...
"docker build" requires exactly 1 argument.
See 'docker build --help'.
        Usage:  docker build [OPTIONS] PATH | URL | -

        Build an image from a Dockerfile

Drats! 'deploy' failed:
'docker build' failed.

authors: SebastianLng bedrierol jkotalik rynowak


text:
How to use a packagemap.json in my project?

I'm trying to automate the upgrade of a very large application with many .csproj using the upgrade-assistant CLI.
I'd like to force certain packages in those .csproj to be updated to certain versions.
The packagemap.json feature seems to support this functionality, But I can't figure out where this file must be placed to be picked up by the cli.
I am running a command like this:
upgrade-assistant upgrade `
			SomeProj/.csproj `
			--non-interactive `
			--operation Inplace `
			--targetFramework net8.0

But my custom defined packagemap.json file is never respected
Where do the packagemap files go? Is this documented anywhere? Is this even how these files are intended to be used?

Take a look at this blog post for how to test package map changes locally: https://devblogs.microsoft.com/dotnet/announcing-api-map-support-for-ua/

Guidance has been provided.

authors: DianaSoltani claudeHasler mgoertz-msft

repo: dotnet/upgrade-assistant


text:
Remove copy command

The shared project moves these files over, so if we can avoid the redundant copy operation, we can save disk space.

Not working on all machines yet

repo: dotnetbio/bio


text:
security vulnerability (存在安全漏洞)

The hard-coded JWT Secret in the source code allows remote attackers to gain administrator access in AgileConfig Server.
Details and POC  have been emailed.
源代码中存在JWT key 硬编码，导致原有的登录限制可能被绕过，直接以管理员权限访问系统
详细信息和POC已发送至邮箱

感谢指出。jwt相关的配置其实都可以使用环境变量来替换，但是估计确实大部分人不会去主动更换，后面的版本我打算在启动的时候生成一个jwt key 来规避这个问题。

v-1.6.8 已修复该问题

你好，agileConfig.Client 最新版本才1.6.2.2 ，怎么升级到1.6.8，这会导致nuget 里面 这个包前面一直带有黄色感叹号

你好，agileConfig.Client 最新版本才1.6.2.2 ，怎么升级到1.6.8，这会导致nuget 里面 这个包前面一直带有黄色感叹号

其实这个漏洞跟client没关系，client根本走的不是jwt认证。但是GitHub的策略好像觉得这个client也要更新。你就用最新的1622好了没关系的。我有空修改个版本号消除这个感叹号。

authors: JavaScript-zt kklldog poq79

repo: dotnetcore/AgileConfig


text:
我想问一下大家，框架好用吗？

技术选型中，时间不多，我也不是大牛，想省一点时间 问一下大家，框架好用吗？

1.0 版本还没出  等吧

这样啊，我以为已经是可用状态了

surging 1.0 版本只是定义为标准完整版本, 所有的功能都已经实现，1.0并不能代表什么，也许surging 1.0可以看作其它框架的3.0，各个公司定义的含义不一样，就像Oracle发布的第一个不稳定版本，直接定义为2.0，因为潜在的客户更愿意购买第2个版本，而不是初始版本。

这么说，只要我熟悉了，可投入生产了？

这个就需要你们自己评估，只是告诉你已经有人开始使用， 从nuget，docker镜像库，github下载量来看应该有至少好几家公司在使用。

会不会是学习中？

感谢

authors: fanliang11 gebiWangshushu windsOne

repo: dotnetcore/surging


text:
🛑 Biseri-jadrana.si is down

In 1956c10, Biseri-jadrana.si (https://www.biseri-jadrana.si/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Biseri-jadrana.si is back up in 55742be after 12 minutes.

repo: dotsi/bitamiuptime


text:
🛑 JustBlameBen4Everything is down

In 7f9c0ca, JustBlameBen4Everything (https://justblameben4everything.online) was down:

HTTP code: 0
Response time: 0 ms

Resolved: JustBlameBen4Everything is back up in 8435baf.

repo: dougdragon/uptime