Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Load & build error
wilhelmmedetz
#1 Posted : Tuesday, August 4, 2020 4:50:33 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 7/4/2012(UTC)
Posts: 31

Was thanked: 2 time(s) in 2 post(s)
Hi,

when trying to switch to a new computer the following error occurred.

The exactly same solution builds on an other computer without any problems.
Main difference between the two systems: this one has more cores and memory (software configuration should be roughly the same).
When loading the solution NCrunch shows the following error (never had this before):
Quote:
There are projects in this solution that have not been reported as loaded by the IDE during NCrunch initialisation. It is possible that these projects are of an unusual type and NCrunch has been unable to correctly detect them, or they may be 'unloaded' in Visual Studio.

If these projects are not required for your NCrunch session, it is recommended that you ignore them using the NCrunch 'Ignore this component completely' configuration setting.

The following projects exist in this solution but could not be resolved by NCrunch during initialisation:

C:\Dev\KEBA\Keba.Xfs.Core\Keba.Xfs.TestUtils\Keba.Xfs.TestUtils.csproj
C:\Dev\KEBA\Keba.Xfs.Core\Keba.Xfs.CoreEx\Keba.Xfs.CoreEx.csproj
C:\Dev\KEBA\Keba.Xfs.Core\Keba.Xfs.CoreEx.Tests\Keba.Xfs.CoreEx.Tests.csproj
C:\Dev\KEBA\Keba.Xfs.Core\Keba.Xfs.Notification.Data\Keba.Xfs.Notification.Data.csproj
C:\Dev\KEBA\Keba.Xfs.Core\Keba.Xfs.Notification.Client\Keba.Xfs.Notification.Client.csproj
C:\Dev\KEBA\Keba.Xfs.Core\Keba.Xfs.Provider.Spock\Keba.Xfs.Provider.Spock.csproj
C:\Dev\KEBA\Keba.Xfs.Core\Keba.Xfs.Provider.Spock.Tests\Keba.Xfs.Provider.Spock.Tests.csproj

Click here to remove this error

Visual Studio has all projects loaded and builds without problems.
The NCrunch Processing Queue dieplay the following error for two projects (these two projects have been reportes as not loaded above).
Adding ProductVersion,cs to 'Additional files to include' makes no difference.
Quote:
[18:33:12.0893-LocalBuildTask-9] ERROR (Internal): System.Exception: Code file C:\Dev\KEBA\Keba.Xfs.Core\ProductVersion.cs has no content to compile
bei nCrunch.Core.BuildManagement.BuildEnvironment.()
bei nCrunch.Core.BuildManagement.BuildEnvironment.Build(SnapshotComponent snapshotComponentToBuild, IList`1 referencedComponents, GridClientId gridClientId, IList`1 customEnvironmentVariables, IPlatformBuildExtender extender, Guid taskId, GridAddress clientAddress)
bei nCrunch.Core.Processing.BuildTaskLogic.DoProcessTaskAndReturnSuccessFlag()
bei nCrunch.Core.Processing.TaskLogic.ProcessTaskAndReturnSuccessFlag()
bei nCrunch.Client.Processing.LocalProcessingTask.ProcessTaskAndReturnSuccessFlag()
bei nCrunch.Client.Processing.ProcessingQueue..()

Other solutions on this computer build without problems.
The problem occurs with NCrunch 4.4 and NCrunch 4.3.

Also submitted a bug report via Visual Studio.

Thanks for your help.

Wilhelm
Remco
#2 Posted : Tuesday, August 4, 2020 11:52:42 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,140

Thanks: 795 times
Was thanked: 1050 time(s) in 1000 post(s)
Hi Wilhelm,

Thanks for sharing this issue.

This looks like it originates from a VS integration issue. VS is not reporting these specific projects internally to NCrunch, so NCrunch can't find them.

Can you check if you are running the same version of VS on your new machine? You may need to reinstall it.

Edit: I've just reviewed the bug report you submitted and found the following exception:

System.Text.DecoderFallbackException: Die Bytes [96] im Index 903 k?nnen nicht von der angegebenen Codepage in Unicode ?bersetzt werden.
bei System.Text.DecoderExceptionFallbackBuffer.Throw(Byte[] bytesUnknown, Int32 index)
bei System.Text.DecoderExceptionFallbackBuffer.Fallback(Byte[] bytesUnknown, Int32 index)
bei System.Text.DecoderFallbackBuffer.InternalFallback(Byte[] bytes, Byte* pBytes)
bei System.Text.UTF8Encoding.GetCharCount(Byte* bytes, Int32 count, DecoderNLS baseDecoder)
bei System.String.CreateStringFromEncoding(Byte* bytes, Int32 byteLength, Encoding encoding)
bei System.Text.UTF8Encoding.GetString(Byte[] bytes, Int32 index, Int32 count)
bei nCrunch.Client.ComponentMemberFileLoader.LoadMemberContentIfChanged(SnapshotComponentMember member)
bei nCrunch.Client.Synchronisation.SnapshotSynchroniser.(FilePath , SnapshotComponent[] )
bei nCrunch.Client.Synchronisation.SnapshotSynchroniser..(FilePath , SnapshotComponent[] )
bei nCrunch.Client.Initialisation.ProjectLoadInitTask.Run()
bei nCrunch.Common.ErrorHandler.DoWithErrorHandling(Action action, Object context)

I'm not sure yet if this is downstream from the VS integration issue or if it is the cause of the problem. It's possible this may be caused by an encoding problem in at least one of your files. Check to see if closing all the source files in the IDE makes any difference. Try installing any language packs on your new machine that may have been on your old one.
wilhelmmedetz
#3 Posted : Wednesday, August 5, 2020 7:50:10 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 7/4/2012(UTC)
Posts: 31

Was thanked: 2 time(s) in 2 post(s)
Hi Remco,

VS version and installed components should be the same (except that VS was updated continuously over one year on the older machine).

Disabling all other extensions made no difference.

Why does NCrunch try to build Keba.Xfs.TestUtils.csproj and Keba.Xfs.CoreEx.csproj although it states, that it could not resolve these projects?

I inspected ProductVersion.cs in the project workspace folders of the above projects and they seem to be correct.

Language packs should be the same.

I copied the complete solution directly from the other system. I can not find any differences in the source files. VS builds the solution without problem.
Remco
#4 Posted : Thursday, August 6, 2020 1:49:31 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,140

Thanks: 795 times
Was thanked: 1050 time(s) in 1000 post(s)
Would you be interested in trying the build below? I've made an improvement to the error handling in this area. When NCrunch encounters a file with unknown encoding, it will now report the error in a consistent manner including the name of the file involved. You should be able to use this build to establish which files are triggering the issue. When you know which files are involved, you can fix up their encoding and hopefully get past the problem:

NCrunch_Console_4.5.0.1.msi
NCrunch_Console_4.5.0.1.zip
NCrunch_GridNodeServer_4.5.0.1.msi
NCrunch_GridNodeServer_4.5.0.1.zip
NCrunch_LicenseServer_4.5.0.1.zip
NCrunch_VS2008_4.5.0.1.msi
NCrunch_VS2010_4.5.0.1.msi
NCrunch_VS2010_4.5.0.1.zip
NCrunch_VS2012_4.5.0.1.msi
NCrunch_VS2012_4.5.0.1.zip
NCrunch_VS2013_4.5.0.1.msi
NCrunch_VS2013_4.5.0.1.zip
NCrunch_VS2015_4.5.0.1.msi
NCrunch_VS2015_4.5.0.1.msi.7z
NCrunch_VS2015_4.5.0.1.zip
NCrunch_VS2017_4.5.0.1.msi
NCrunch_VS2017_4.5.0.1.msi.7z
NCrunch_VS2017_4.5.0.1.zip
NCrunch_VS2019_4.5.0.1.msi
NCrunch_VS2019_4.5.0.1.msi.7z
NCrunch_VS2019_4.5.0.1.zip
wilhelmmedetz
#5 Posted : Thursday, August 6, 2020 8:45:50 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 7/4/2012(UTC)
Posts: 31

Was thanked: 2 time(s) in 2 post(s)
With the above version I could finde the files with wring encodings - problems solved.

Thanks for the fast response and help.
Remco
#6 Posted : Friday, August 7, 2020 12:33:28 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,140

Thanks: 795 times
Was thanked: 1050 time(s) in 1000 post(s)
Excellent, thanks for confirming!
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.054 seconds.