Folks, I've been trying to deploy a Blazor app from Visual Studio 2022 for hours without success. I'm doing the usual right-click-publish that I've been doing for about a year, but yesterday it stopped working, and even this morning with a fresh mind I cannot make any progress. I've changed the pubxml options, compile options, etc. Absolutely nothing works. All I get is the generic and utterly useless error below. Normally changing an FTP or Deploy settings :wakes it up" and it works, but not this time. I'm about to delete the publish profile and make a new one, but I'm sure it's a waste of time. I'm wondering if some hosting versions have changed, or something is deprecated, something global I'm not aware of. Has anyone been through this? -- *Greg K* [image: image.png]
Sorry, perhaps dumb question, but what does it say in the Output window? Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile SQL Down Under | Web: https://sqldownunder.com<https://sqldownunder.com/> | About Greg: https://about.me/greg.low From: Greg Keogh via ozdotnet <ozdotnet@ozdotnet.com> Sent: Wednesday, 6 July 2022 10:23 AM To: ozDotNet <ozdotnet@ozdotnet.com> Cc: Greg Keogh <gfkeogh@gmail.com> Subject: Blazor deploy error Folks, I've been trying to deploy a Blazor app from Visual Studio 2022 for hours without success. I'm doing the usual right-click-publish that I've been doing for about a year, but yesterday it stopped working, and even this morning with a fresh mind I cannot make any progress. I've changed the pubxml options, compile options, etc. Absolutely nothing works. All I get is the generic and utterly useless error below. Normally changing an FTP or Deploy settings :wakes it up" and it works, but not this time. I'm about to delete the publish profile and make a new one, but I'm sure it's a waste of time. I'm wondering if some hosting versions have changed, or something is deprecated, something global I'm not aware of. Has anyone been through this? -- Greg K [cid:image001.png@01D89122.D7F20E30]
Sorry, perhaps dumb question, but what does it say in the Output window?
It says "dotnet.exe command failed due to build errors". But there are no errors at all anywhere I look. I just carefully compared my failing app to a newer smaller one that works, and I noticed that the old targets net5.0 and the new one net6.0. Very suspicious. I'm now trying to upgrade to net6.0, but I'm getting weird JS runtime errors, which is a separate hurdle, and if I get over that then I can continue to test if the net version is the problem. Has net5.0 Blazor support been dropped somewhere, either developer client-side or Azure hosting server-side?!? *Greg K*
After hours of ruling out a mistake on my part, or some change in the compile and hosting options, the only thing left is the tooling. Adjusting my searches slightly and haphazardly, I finally stumbled upon this post <https://github.com/dotnet/sdk/issues/26061> from a few weeks ago. Some are blaming spaces in paths, maybe, but I'm using SDK 6.0.301 which people are blaming for introducing this problem. There are some angry comments. I downloaded and installed SDK 6.0.5 with 6.0.300, then ran the command dotnet new globaljson --force --sdk-version 6.0.300 which creates a global.json file as suggested. Clean project, rebuild, now it deploys. The hours of suffering I wasted on this is apparently caused by some bug in the donet command, which someone says will be fixed 6.0.2. I'm shitting bricks and spitting chips, because here we are in 2022 and we get error messages like *An error has occured* with not the slightest clue anywhere about what has gone wrong. In the early 1980s we used to get mainframe messages like "JDE833 Program aborted", but even then I could look up the error in a manual and do something useful. Is this progress?! *Greg K*
Unhappy memories of "redo from start" On Wed, 6 July 2022, 12:15 Greg Keogh via ozdotnet, <ozdotnet@ozdotnet.com> wrote:
After hours of ruling out a mistake on my part, or some change in the compile and hosting options, the only thing left is the tooling. Adjusting my searches slightly and haphazardly, I finally stumbled upon this post <https://github.com/dotnet/sdk/issues/26061> from a few weeks ago.
Some are blaming spaces in paths, maybe, but I'm using SDK 6.0.301 which people are blaming for introducing this problem. There are some angry comments.
I downloaded and installed SDK 6.0.5 with 6.0.300, then ran the command dotnet new globaljson --force --sdk-version 6.0.300 which creates a global.json file as suggested. Clean project, rebuild, now it deploys.
The hours of suffering I wasted on this is apparently caused by some bug in the donet command, which someone says will be fixed 6.0.2.
I'm shitting bricks and spitting chips, because here we are in 2022 and we get error messages like *An error has occured* with not the slightest clue anywhere about what has gone wrong. In the early 1980s we used to get mainframe messages like "JDE833 Program aborted", but even then I could look up the error in a manual and do something useful. Is this progress?!
*Greg K* -- ozdotnet mailing list To manage your subscription, access archives: https://codify.mailman3.com/
https://blog.greglow.com/2018/02/13/opinion-theres-plague-need-stop/ Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile SQL Down Under | Web: https://sqldownunder.com<https://sqldownunder.com/> | About Greg: https://about.me/greg.low From: Greg Keogh via ozdotnet <ozdotnet@ozdotnet.com> Sent: Wednesday, 6 July 2022 12:43 PM To: ozDotNet <ozdotnet@ozdotnet.com> Cc: Greg Keogh <gfkeogh@gmail.com> Subject: Re: Blazor deploy error After hours of ruling out a mistake on my part, or some change in the compile and hosting options, the only thing left is the tooling. Adjusting my searches slightly and haphazardly, I finally stumbled upon this post<https://github.com/dotnet/sdk/issues/26061> from a few weeks ago. Some are blaming spaces in paths, maybe, but I'm using SDK 6.0.301 which people are blaming for introducing this problem. There are some angry comments. I downloaded and installed SDK 6.0.5 with 6.0.300, then ran the command dotnet new globaljson --force --sdk-version 6.0.300 which creates a global.json file as suggested. Clean project, rebuild, now it deploys. The hours of suffering I wasted on this is apparently caused by some bug in the donet command, which someone says will be fixed 6.0.2. I'm shitting bricks and spitting chips, because here we are in 2022 and we get error messages like An error has occured with not the slightest clue anywhere about what has gone wrong. In the early 1980s we used to get mainframe messages like "JDE833 Program aborted", but even then I could look up the error in a manual and do something useful. Is this progress?! Greg K
https://blog.greglow.com/2018/02/13/opinion-theres-plague-need-stop/
Ha! I owe you a drink. I thought I was crazy, but I'm relieved to know I'm not alone -- *GK*
I kinda like .DMP files, especially if I've got a matching set of pdb files to match it. On Wed, 6 July 2022, 12:57 Dr Greg Low via ozdotnet, <ozdotnet@ozdotnet.com> wrote:
https://blog.greglow.com/2018/02/13/opinion-theres-plague-need-stop/
Regards,
Greg
Dr Greg Low
1300SQLSQL (1300 775 775) office | +61 419201410 mobile
SQL Down Under | Web: https://sqldownunder.com | About Greg: https://about.me/greg.low
*From:* Greg Keogh via ozdotnet <ozdotnet@ozdotnet.com> *Sent:* Wednesday, 6 July 2022 12:43 PM *To:* ozDotNet <ozdotnet@ozdotnet.com> *Cc:* Greg Keogh <gfkeogh@gmail.com> *Subject:* Re: Blazor deploy error
After hours of ruling out a mistake on my part, or some change in the compile and hosting options, the only thing left is the tooling. Adjusting my searches slightly and haphazardly, I finally stumbled upon this post <https://github.com/dotnet/sdk/issues/26061> from a few weeks ago.
Some are blaming spaces in paths, maybe, but I'm using SDK 6.0.301 which people are blaming for introducing this problem. There are some angry comments.
I downloaded and installed SDK 6.0.5 with 6.0.300, then ran the command dotnet new globaljson --force --sdk-version 6.0.300 which creates a global.json file as suggested. Clean project, rebuild, now it deploys.
The hours of suffering I wasted on this is apparently caused by some bug in the donet command, which someone says will be fixed 6.0.2.
I'm shitting bricks and spitting chips, because here we are in 2022 and we get error messages like *An error has occured* with not the slightest clue anywhere about what has gone wrong. In the early 1980s we used to get mainframe messages like "JDE833 Program aborted", but even then I could look up the error in a manual and do something useful. Is this progress?!
*Greg K* -- ozdotnet mailing list To manage your subscription, access archives: https://codify.mailman3.com/
That’s cute. However, even that doesn’t work now when so many errors returned to UIs only include a GUID that’s unique to that instance of the error. Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile SQL Down Under | Web: https://sqldownunder.com<https://sqldownunder.com/> | About Greg: https://about.me/greg.low From: mike smith via ozdotnet <ozdotnet@ozdotnet.com> Sent: Wednesday, 6 July 2022 2:03 PM To: ozDotNet <ozdotnet@ozdotnet.com> Cc: mike smith <meski.oz@gmail.com> Subject: Re: Blazor deploy error I kinda like .DMP files, especially if I've got a matching set of pdb files to match it. On Wed, 6 July 2022, 12:57 Dr Greg Low via ozdotnet, <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>> wrote: https://blog.greglow.com/2018/02/13/opinion-theres-plague-need-stop/ Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile SQL Down Under | Web: https://sqldownunder.com<https://sqldownunder.com/> | About Greg: https://about.me/greg.low From: Greg Keogh via ozdotnet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>> Sent: Wednesday, 6 July 2022 12:43 PM To: ozDotNet <ozdotnet@ozdotnet.com<mailto:ozdotnet@ozdotnet.com>> Cc: Greg Keogh <gfkeogh@gmail.com<mailto:gfkeogh@gmail.com>> Subject: Re: Blazor deploy error After hours of ruling out a mistake on my part, or some change in the compile and hosting options, the only thing left is the tooling. Adjusting my searches slightly and haphazardly, I finally stumbled upon this post<https://github.com/dotnet/sdk/issues/26061> from a few weeks ago. Some are blaming spaces in paths, maybe, but I'm using SDK 6.0.301 which people are blaming for introducing this problem. There are some angry comments. I downloaded and installed SDK 6.0.5 with 6.0.300, then ran the command dotnet new globaljson --force --sdk-version 6.0.300 which creates a global.json file as suggested. Clean project, rebuild, now it deploys. The hours of suffering I wasted on this is apparently caused by some bug in the donet command, which someone says will be fixed 6.0.2. I'm shitting bricks and spitting chips, because here we are in 2022 and we get error messages like An error has occured with not the slightest clue anywhere about what has gone wrong. In the early 1980s we used to get mainframe messages like "JDE833 Program aborted", but even then I could look up the error in a manual and do something useful. Is this progress?! Greg K -- ozdotnet mailing list To manage your subscription, access archives: https://codify.mailman3.com/
This thread was held up in moderation because of the size of it. I've changed the limit on the server to 2meg per message up from the 1meg I had. Mailman ships with 20KB per message as the limit... reminds me of the quaint old days of the internet in the early 90s when people would tear you a new one for wasting bandwidth by having an e-mail signature that was too big. David Connors david@connors.com | M +61 417 189 363 Telegram: https://t.me/davidconnors LinkedIn: http://au.linkedin.com/in/davidjohnconnors On Wed, 13 Jul 2022 at 09:15, Dr Greg Low via ozdotnet < ozdotnet@ozdotnet.com> wrote:
That’s cute.
However, even that doesn’t work now when so many errors returned to UIs only include a GUID that’s unique to that instance of the error.
Regards,
Greg
Dr Greg Low
1300SQLSQL (1300 775 775) office | +61 419201410 mobile
SQL Down Under | Web: https://sqldownunder.com | About Greg: https://about.me/greg.low
*From:* mike smith via ozdotnet <ozdotnet@ozdotnet.com> *Sent:* Wednesday, 6 July 2022 2:03 PM *To:* ozDotNet <ozdotnet@ozdotnet.com> *Cc:* mike smith <meski.oz@gmail.com> *Subject:* Re: Blazor deploy error
I kinda like .DMP files, especially if I've got a matching set of pdb files to match it.
On Wed, 6 July 2022, 12:57 Dr Greg Low via ozdotnet, < ozdotnet@ozdotnet.com> wrote:
https://blog.greglow.com/2018/02/13/opinion-theres-plague-need-stop/
Regards,
Greg
Dr Greg Low
1300SQLSQL (1300 775 775) office | +61 419201410 mobile
SQL Down Under | Web: https://sqldownunder.com | About Greg: https://about.me/greg.low
*From:* Greg Keogh via ozdotnet <ozdotnet@ozdotnet.com> *Sent:* Wednesday, 6 July 2022 12:43 PM *To:* ozDotNet <ozdotnet@ozdotnet.com> *Cc:* Greg Keogh <gfkeogh@gmail.com> *Subject:* Re: Blazor deploy error
After hours of ruling out a mistake on my part, or some change in the compile and hosting options, the only thing left is the tooling. Adjusting my searches slightly and haphazardly, I finally stumbled upon this post <https://github.com/dotnet/sdk/issues/26061> from a few weeks ago.
Some are blaming spaces in paths, maybe, but I'm using SDK 6.0.301 which people are blaming for introducing this problem. There are some angry comments.
I downloaded and installed SDK 6.0.5 with 6.0.300, then ran the command dotnet new globaljson --force --sdk-version 6.0.300 which creates a global.json file as suggested. Clean project, rebuild, now it deploys.
The hours of suffering I wasted on this is apparently caused by some bug in the donet command, which someone says will be fixed 6.0.2.
I'm shitting bricks and spitting chips, because here we are in 2022 and we get error messages like *An error has occured* with not the slightest clue anywhere about what has gone wrong. In the early 1980s we used to get mainframe messages like "JDE833 Program aborted", but even then I could look up the error in a manual and do something useful. Is this progress?!
*Greg K*
-- ozdotnet mailing list To manage your subscription, access archives: https://codify.mailman3.com/
-- ozdotnet mailing list To manage your subscription, access archives: https://codify.mailman3.com/
Hah, https://wiki.c2.com/?TrimYourPosts <insert 56k modem sounds here> Speaking of email signatures, on the list I find myself referring to them more often as it's become harder determine the message origin since the cutover. All messages are now showing as "From: ozDotNet" now, with an mix of To: and Cc: from those who have replied in the thread. Is anyone else seeing this also, is this a mailman setting? Example: https://imgur.com/a/s1x3fMJ -Tony On 13/07/2022 09:18, David Connors via ozdotnet wrote:
This thread was held up in moderation because of the size of it. I've changed the limit on the server to 2meg per message up from the 1meg I had. Mailman ships with 20KB per message as the limit... reminds me of the quaint old days of the internet in the early 90s when people would tear you a new one for wasting bandwidth by having an e-mail signature that was too big.
David Connors david@connors.com <mailto:david@connors.com> | M +61 417 189 363 Telegram: https://t.me/davidconnors LinkedIn: http://au.linkedin.com/in/davidjohnconnors
On Wed, 13 Jul 2022 at 11:41, Tony McGee via ozdotnet <ozdotnet@ozdotnet.com> wrote:
Speaking of email signatures, on the list I find myself referring to them more often as it's become harder determine the message origin since the cutover. All messages are now showing as "From: ozDotNet" now, with an mix of To: and Cc: from those who have replied in the thread. Is anyone else seeing this also, is this a mailman setting?
Example: https://imgur.com/a/s1x3fMJ
The new list is set to have a from address of ozdotnet@ozdotnet.com with a display name of the poster. I think the issue is whatever e-mail client that is is not showing the display name ... ? THis is what I see in gmail.... [image: image.png]
participants (5)
-
David Connors -
Dr Greg Low -
Greg Keogh -
mike smith -
Tony McGee