> Abrir terminal

• Abre o Terminal ou PowerShell na pasta do projeto Blazor (onde está o .csproj). cd C:\caminho\do\projeto

> Rodar o comando

• Para Blazor Server: dotnet watch run
• Para Blazor WebAssembly (com ASP.NET Core host) também serve o mesmo comando.

Isso vai:

• Compilar o projeto.
• Subir um servidor local (normalmente em https://localhost:5001).
• Ficar observando alterações nos arquivos .razor, .cs, .css.
• Recarregar automaticamente o navegador quando salvar algo.

• Usa CLI:

dotnet new blazorserver -n MeuProjeto -f net8.0
cd MeuProjeto
dotnet watch run

SE Kestrel quer HTTPS mas não tens dev-cert válido

Porque isto acontece

• dotnet watch run força HTTPS
• Não tens developer certificate instalado/válido
• Resultado: Kestrel não arranca ? crash imediato

Corre como admin:

dotnet dev-certs https --clean
dotnet dev-certs https --trust

Fecha o browser, volta a correr:

dotnet watch run

Once you disabled the recovery partition, you can just launch diskpart and complete the changes.

you’ll be able to

1. delete the recovery parttion
2. extend your C: partition to a desired size
3. recreate the recovery partition with the correct type
4. format the recovery partition

1. identify and delete recovery partition

so, first you need to disable it, that’s the already known command:

reagentc /disable

with that done, launch diskpart

where you pick your OS drive by ID and the recovery partition by ID. And then you delete it. This is possible using the override keyword asking Windows to not consider that protected partition a protected protected partition for that short moment where you delete it.

list disk  #< identify OS drive here, example below is 'disk 0'
sel disk 0
list part  #< identify recovery partitition here, example below is 'part 3'
sel part 3
delete part override

2. resize your C: partition

where you select your OS partition by ID and increase its size – while leaving space for the recovery partition’s recreation. The partition resize automatically triggers the filesystem resize.

list part #< OS partition, C:\ Drive letter is part 2 in example below
sel part 2
extend size=112000

3. create recovery partition

where you re-create the recovery partition for later use. if you (reader, not OP) has a UEFI system this command will DIFFER. See Microsoft KB5028997 for details about that.

3.1 Basic Disks

create partition primary size=1000 id=27

3.2 GPT Disks

On GPT disks, you’ll get an error about incorrect syntax for this. There use:

create partition primary size=1000 id=de94bba4-06d1-4d40-a16a-bfd50179d6ac

If this worked, the new partition is auto-selected and can be formatted. If it didn’t work, then please stop here and debug.

format quick fs=ntfs label="Windows RE tools"
exit

Note:

1. You can then use the partition ID from @AdamKalisz’s comment below!
2. The newly created partition is automatically selected by diskpart.
3. You want a size of 1GB for the partition to avoid errors from windows Upgrade (that’s the 0x80070643 error code). It can hit the error condition when updating the recovery code (done via windows update).

4. enable recovery partition

now you can re-enable the new recovery partition

reagentc /enable

That’s it. I had to do this a few days ago, and there’s really no need to have a downtime for this. You might still need to reboot for the update, but at least it’ll be at a time of your chosing.

If the update error doesn’t go away, you might want to investigate windows update client issues.

5. When your system never had a valid RE image

There’s also an edge case if there’s no valid copy of the recovery image on disk – there still can be a partition, but it might be invalid. I’ve also seen cases with 3 rescue partitions.

5.1 Mounting a WIM image and extracting the WinRE boot image

In such cases, you can proceed – but: you might need to re-genererate the RE image. This works along the lines what is described here: https://www.elevenforum.com/t/deleted-windows-recovery-partition-how-to-make-a-new-one.11534/

5.2 Working with readonly (DVD) media

Just note that you might need to change some flags for dism to work with a readonly image. i.e. I needed dism /mount-wim [...] /readonly and dism /unmount-wim [...] /discard when working from a dvd image, and then you also need to re-locate the RE path to your actual partition. just check it with /info to be sure it’s in the right spot.

5.3 Don’t lose the security patch!

Since MS updated the RE image in early 2024, you should also make sure that if you use a DVD source that you’ll use one that is recent enough to contain a ‘safe’ winre.wim (*).

(*Footnote: Yes, I know that is tricky or might be nigh impossible on editions like LTSC. I suppose maybe one can then reinstall the januar 24 patch, but I don’t know. I made a life choice to not do windows support decades ago and this is info as far as i’ll bend that rule)

thanks to Florian Heigl

https://superuser.com/questions/1354574/how-to-expand-the-windows-partition-when-the-recovery-one-is-in-the-way

DBCC SQLPERF(LOGSPACE);  --  Checks the space used by the log
DBCC OPENTRAN ('mydb');  -- Checks for open transactions in the database
BACKUP LOG mydb TO DISK = 'C:\_Backup\mydb_log.bak';  --  Backs up the log (required in FULL mode)
DBCC SHRINKFILE (N'mydb_log', TRUNCATEONLY);  -- Shrinks the log file, freeing up unused space

Stop backup log:

SELECT session_id, command, status, start_time FROM sys.dm_exec_requests WHERE command = ‘BACKUP DATABASE’ OR command = ‘BACKUP LOG’;

KILL sesionid;

Receive:
Default Frontend xxxx/EXCH01

Send:
Outbound to Office 365
xxxxx send connector

If you try to delete the old certificate, without setting the new cert for the connectors, you will get this in ECP:
“A special Rpc error occurs on server EXCH01: These certificates are tagged with following Send Connectors : Outbound to Office 365. Removing and replacing certificates from Send Connector would break the mail flow. If you still want to proceed then replace or remove these certificates from Send Connector and then try this command.”

So we need to move into Powershell and replace it, because it cannot be done through the ECP:

Get the thumprint for the new cert:

Get-ExchangeCertificate

So here it is, the top level cert, it’s a wildcard cert, thus the “*.” in the subject name, sorry for the maskings, this is from a non-lab environment

Copy the thumprint to notepad for next command.

Read the certificate subject and thumprint into a variable:

$cert = Get-ExchangeCertificate -Thumbprint <paste the thumbprint in here from previous command>

$tlscertificatename = "<i>$($cert.Issuer)<s>$($cert.Subject)" - Do not change anything here!

The replace the connectors:

Send Connector –

Set-SendConnector "Outbound to Office 365" -TlsCertificateName $tlscertificatename

Receive Connector –

Set-ReceiveConnector "EXCH01\Default Frontend EXCH01" -TlsCertificateName $tlscertificatename

Note: replace the word “EXCH01” with the name of your Exchangeserver like “MY-EXCH01\Default Frontend MY-EXCH01”

Run IISRESET

This is because the old and new certificate have the same “issuer” and “subject”, the set-sendconnector and set-receiveconenctor, cannot thereforem tell the difference, but solution is easy:

Just add another cert on the servers thumbprint to the first script, then run all commands throgh, after that, do the same again, but now with the real cert’s thumprint, and it works ?

Note that if you fail to replace your certificate before it expires (You forgot to), your mailflow between on-prem Excahnge and Exchange Online (365) will stop working and you will see this in the logs:

[Message=451 5.7.3 STARTTLS is required to send mail]

source links:

https://martinsblog.dk/exchange-replacing-certificate-for-microsoft-365-hybrid-connectors/
https://martinsblog.dk/exchange-an-error-occurred-while-using-ssl-configuration-for-endpoint-0-0-0-0444/
https://www.azure365pro.com/replacing-send-connector-certificate/

To install or uninstall ASP.NET 4.5 in Windows 8 or Windows Server 2012, use one of the following options:

• Run the following command from an administrative command prompt: Console

dism /online /enable-feature /featurename:IIS-ASPNET45

For Windows 8 client computers, turn on IIS-ASPNET45 in Turn Windows Features On/Off under Internet Information Services > World Wide Web Services > Application Development Features > ASP.NET 4.5.

For Windows Server 2012 computers, enable IIS-ASPNET45 using Server Manager, under Web Server (IIS) > Web Server > Application Development > ASP.NET 4.5.

I receive information from another page from a payment gateway. On the admin panel i can assign the callback url to notify me.

it will respond with a json payload.

How to get this info in codebehind on Page_load?

Make sure that, if you are using Friendly urls that the callback url has no .aspx

and try something like:

Public Shared Function GetRequestBody() As String
    Dim bodyStream = New IO.StreamReader(HttpContext.Current.Request.InputStream)
    bodyStream.BaseStream.Seek(0, SeekOrigin.Begin)
    Dim _payload = bodyStream.ReadToEnd()
    Return _payload
End Function

thanks to https://stackoverflow.com/questions/71097260/how-can-i-get-information-in-network-payload-using-c

Restart BITS service and try the operation again. Also make sure that the client has permissions on the source and the destination.

ID: 24366

Possible resolution:

Restart BITS (Background Intelligent Transfer Service)

Delete the expired certificate from the VMM server’s Personal Store and create a new one:

[PowerShell]:

$credential = get-credential

Get-VMMManagedComputer -ComputerName “VMM-Server.domain.com” | Register-SCVMMManagedComputer -Credential $credential

You will now get a new certificate which is valid for 5 years.

try
Get-SCVMMServer if command not recognized.

We use Windows Server 2008 R2 Datacenter x64 in this example.

Open Exchange Management Shell as Administrator and get a list of SSL certificates that are available:

[PS]> Get-ExchangeCertificate

Thumbprint                    Services  Subject
----------                              --------  -------
1F70359DC0BE9CAD58F965A3C110  ...WS.    CN=*.example.com, OU=IT Dep, O=Example Comp...
0F7FF199B11E662621D80700D04F  ....S.    CN=ExampleDC

When you enable the wildcard *.example.com certificate for POP service, you normally get the following error:

PS]> Enable-ExchangeCertificate -Thumbprint 1F70359DC0BE9CAD58F965A3C110 -Services POP
WARNING: This certificate with thumbprint 1F70359DC0BE9CAD58F965A3C110 and subject '*.example.com' cannot used for POP SSL/TLS connections because the subject is not a Fully Qualified Domain Name (FQDN). Use command Set-POPSettings to set X509CertificateName to the FQDN of the service.

The same applies to IMAP:

[PS]> Enable-ExchangeCertificate -Thumbprint 1F70359DC0BE9CAD58F965A3C110 -Services IMAP
WARNING: This certificate with thumbprint 1F70359DC0BE9CAD58F965A3C110 and subject '*.example.com' cannot used for IMAP SSL/TLS connections because the subject is not a Fully Qualified Domain Name (FQDN). Use command Set-IMAPSettings to set X509CertificateName to the FQDN of the service.

Set FQDN for POP service to fix the error:

[PS]> Set-POPSettings -X509CertificateName exchange2010.example.com

Do the same for IMAP service:

[PS]> Set-IMAPSettings -X509CertificateName exchange2010.example.com

Verify POP settings:

[PS]> Get-POPSettings

UnencryptedOrTLSBindings  SSLBindings            LoginType    X509CertificateName
------------------------  -----------            ---------    -------------------
{:::110, 0.0.0.0:110}     {:::995, 0.0.0.0:995}  SecureLogin  exchange2010.example...

Verify IMAP settings:

[PS]> Get-IMAPSettings

UnencryptedOrTLSBindings  SSLBindings            LoginType    X509CertificateName
------------------------  -----------            ---------    -------------------
{:::143, 0.0.0.0:143}     {:::993, 0.0.0.0:993}  SecureLogin  exchange2010.example...

Restart POP and IMAP services:

[PS]> Restart-service MSExchangePOP3
[PS]> Restart-service MSExchangeIMAP4

Source link:

https://www.lisenet.com/2014/configure-wildcard-ssl-certificate-for-pop-imap-on-exchange-2010-server/

You have to set the cookieSameSite= “None” in the session state tag to avoid this issue. I have tried this and working well.

<system.web>
<sessionState cookieSameSite="None"  cookieless="false" timeout="360">
</sessionState> 
</system.web>

https://social.msdn.microsoft.com/Forums/en-US/1b99630c-299c-446e-bf4b-d7d4d74bf9ef/problem-with-session-in-iframe-after-recent-windows-update?forum=aspstatemanagement