For some reason I could not update my VS 2013 license today! The service was not available until I entered these registry Keys!

How to enable Transport Layer Security (TLS) 1.2 on clients - Configuration Manager | Microsoft Learn

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions" = dword:00000001
"SchUseStrongCrypto" = dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions" = dword:00000001
"SchUseStrongCrypto" = dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions" = dword:00000001
"SchUseStrongCrypto" = dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions" = dword:00000001
"SchUseStrongCrypto" = dword:00000001

I received the following error when I was attempting to compare columns in a SQL query between two tables located in two separate databases. In this case, the collation settings between the two databases were configured differently. Rather make any changes to the databases, I was able to apply a simple fix to my SQL query: In fact even when I changed the Collation in the Database it still did not Join!

ORIGINAL QUERY –

SELECT        TOP (100) PERCENT dbo.MyLoans.LoanNumber AS [Loan Number], LoansDW.dbo.TAP.BorrFirstName AS [PB First], LoansDW.dbo.TAP.BorrLastName AS [PB Last]

FROM            EncompassDW.dbo.TAP RIGHT OUTER JOIN

                         dbo.FiveStarLoans ON LoansDW.dbo.TAP.LoanNumber = dbo.FiveStarLoans.LoanNumber 

ORDER BY [Loan Number]

FIX –

Simply apply the default collation to the fields you are comparing.

SELECT        TOP (100) PERCENT dbo.MyLoans.LoanNumber AS [Loan Number], LoansDW.dbo.TAP.BorrFirstName AS [PB First], LoansDW.dbo.TAP.BorrLastName AS [PB Last]

FROM            EncompassDW.dbo.TAP RIGHT OUTER JOIN

                         dbo.FiveStarLoans ON LoansDW.dbo.TAP.LoanNumber = dbo.FiveStarLoans.LoanNumber COLLATE DATABASE_DEFAULT

ORDER BY [Loan Number]

Also here: Event ID 6398 (microsoft.com)

The Execute method of job definition Microsoft.SharePoint.Administration.SPAppStateQueryJobDefinition (ID e7ddc5b6-3089-4108-a8ed-4adc453c7c60) threw an exception. More information is included below.
One or more app state queries have failed.
What can I do to fix this also this is for sharepoint 2013 Foundation or whatever the free version is called

Answer:

Go to the SharePoint Central Administration
Click Monitoring
Then click Review job definitions in the Timer Jobs section
Find the Job that is causing the exception by hovering over the links and checking the GUID in there
Click the job and click Disable

https://sharepoint.stackexchange.com/questions/211920/sharepoint-2013-custom-display-form-time-date-not-formatted-correctly

Date showing as Universal Date: 2021-03-21T13:00:00Z

<xsl:value-of select="ddwrt:FormatDateTime(string(@Other_x0020_MyStuff_x0020__x0),1037, 'MM/d/yyyy')"/>

After a SharePoiint Foundation 2010 to SharePoint Foundation 2013 upgrade, hidden fields were showing up again UNTIL the JavaScript line was added into the Edit Page via SharePoint Designer 2013.

<asp:Content ContentPlaceHolderId="PlaceHolderMain" runat="server">
<script type="text/javascript" src="/sites/lng/Style%20Library/jquery/jquery-3.6.0.min.js"></script>
<script type="text/javascript">
$(document).ready(function(){
$("nobr:contains('Project Registration Date')").closest('tr').hide();
$("nobr:contains('Drawing Review Date')").closest('tr').hide();
$("nobr:contains('Design Contractor')").closest('tr').hide();
$("nobr:contains('Project Initiation Date')").closest('tr').hide();
$("nobr:contains('Installed By')").closest('tr').hide();
$("nobr:contains('Cat.')").closest('tr').hide();
$("input[title*='B defs. (Initial)']").closest('tr').hide();
$("input[title*='B defs. (Remaining)']").closest('tr').hide();
$("input[title*='A defs. (Initial)']").closest('tr').hide();
$("input[title*='A defs. (Remaining)']").closest('tr').hide();
$("nobr:contains('C.R.s')").closest('tr').hide();
});
</script>

This occured after a SharePoint 2010 Foundation to SharePoint 2013 Foundation upgrade.

https://www.ozkary.com/2012/06/sharepoint-custom-form-shows-html-as.html

SharePoint Custom Form Shows HTML as Text on Lookup Fields

Before: <xsl:value-of select="@FieldName" />

After: <xsl:value-of select="@FieldName" disable-output-escaping="yes"/>

BEFORE

AFTER

Making the Sub-Report wider will fix this issue!

Log onto the Azure Portal, go to the App Services and select the App that you need to publish from Visual Studio to Azure.

Click on Get publish Profile. This downloads a Settings file.

In Visual Studio go to Publish and selete the "Import Profile" option.

Then import the Profile that you just exported from Azure. Done!

On local SQL Server database right-click on the database, Tasks, then Export Data-Tier Application to create a *.bacpac file.

Connect to the Azure database server via SSMS. Right-Click on the Azure Databases node. The Database cannot currently exist, so if it does it needs to be deleted first!

Select Import Data-tier Application and select the *.bacpac files that was created in the first step. This creates the database in Azure!

Don't forget to select the Edition of Microsoft Azure SQL Database before you complete the process.

More Info Here: https://stackoverflow.com/questions/21098333/visual-studio-compiles-fine-but-it-still-shows-red-lines Visual Studio 2019 is showing red underline all the time, even when it compiles fine!

Closing Visual Studio and removing the .vs folder located in the solution directory worked for me.

This folder has a hidden attribute. You may need to change settings in folder options to show hidden files.