(I guess if checking if URL is already taken, e.g. Site exists, but you don't have access. If (IsUnableToAccessSiteException(ex) || IsCannotGetSiteException(ex)) TestContext.Load(testContext.Web, w => w.Title) Using (ClientContext testContext = context.Clone(webFullUrl))
#Resharper 9 unit tests greyed out code
code of WebExtensions.WebExistsFullUrl method is still the same: public static bool WebExistsFullUrl(ClientRuntimeContext context, string webFullUrl) I checked this issue with the latest PnP version (which is at the moment of writing of this article) and found that this problem is fixed now by MS.
Also I posted issue to PnP-Sites-Core in github: WebExtensions.WebExistsFullUrl returns true for non-existent sites from different managed path in Sharepoint 2013 on-premise.
#Resharper 9 unit tests greyed out how to
Full description of the problem is available here: How to check does site collection exist by absolute url using CSOM in Sharepoint. You can now create sensitivity labels with privacy and access control settings for Teams, SharePoint sites, and Microsoft 365 Groups.įew years ago I wrote about one problem in OfficeDevPnP method WebExtensions.WebExistsFullUrl: shortly when it was called with url which belongs to non-existent site collection from different managed path it returned true. Pay attention that there is now the following note: Let’s see how it looks like in Security and compliance center > Classification > Sensitivity labels. If you will have error "It is about Unable to resolve package source ” then start new PowerShell session as administrator and run the following command as 1st command in the session: ::SecurityProtocol = ::Tls12Īfter these steps you will be able to create sensitivity labels for SP sites, Teams and O365 groups. After that we need to sync them to AzureAD using the following script: Install-Module -Name ExchangeOnlineManagementĬonnect-IPPSSession -Credential $UserCredential $Setting = Get-AzureADDirectorySetting -Id (Get-AzureADDirectorySetting | where -Property DisplayName -Value "Group.Unified" -EQ).id First of all enable sensitivity labels from PowerShell using the following script: Import-Module AzureADPreview Sensitivity labels may be enabled from several places:īy default they can be used for files in emails but in order to enable them for “container” (SP online sites, Teams and O365 groups) several additional steps should be done:ġ. don’t have O365 policies assigned to them) sensitivity labels have policies behind and allow to use O365 infrastructure to maintain sensitive data in your organization. In opposite to classification labels which are more like additional metadata for O365 groups/SP sites where custom policies have to be enforced by internal tools or custom PowerShell scripts (i.e. Sensitivity labels help to maintain content in your organization. This error will be still there even if “Integrate with other runners” option will be checked in Typemock menu: use 'TypeMockStart' tasks for MSBuild or NAntįor more information consult the documentation (see 'Running Unit Tests in an Automated Build')Īt () run tests via TMockRunner.exe command line tool * To run Typemock Isolator as part of an automated process you can:
For other runners, Choose Typemock Menu and click "Integrate with Other Runners" *** Typemock Isolator is currently disabled. If you use TypeMock isolator for writing unit tests (which is great library for mocking from my point of view) and ReSharper to make user experience in Visual Studio better (which is another great tool :) ) then you may face with the following problem when try to run unit tests in ReSharper test runner: tests will fail with the following error