Project creation with Template Studio fails

[Lothar Behrens]

Hi,

after getting my Community license I started to try creating a new project. After fiddling and searching, I had to install additional components within the installer and then also install an extension for Visual Studio 2017.

When I create a new project, I chose Ribbon and a grid control. I tested it with different .NET target versions.

I have Visual Studio in Professional for 2012, 2017 and 2022. I had Visual Studio 2022 Community short time before.

Basic question is as follows: Did I messed up with those many Visual Studio versions installed? :-)

Running existing examples was possible, but there I had errors before (had to clean the projects after playing with my Visual Studio versions).

Thanks

Lothar

Error (as well in 2022):

System.Exception: Fehler bei der Ausführung von „Microsoft.Templates.Core.PostActions.Catalog.AddContextItemsToSolutionAndProjectPostAction“. Verwandte Vorlage: None. ---> System.Exception: Fehler beim Hinzufügen von Projekt C:\Users\Lothar\source\repos\SyncfusionWinFormsApp1\SyncfusionWinFormsApp1\SyncfusionWinFormsApp1.csproj ---> Microsoft.Build.Exceptions.InvalidProjectFileException: Der Ausdruck "[Microsoft.Build.Utilities.ToolLocationHelper]::GetPathToStandardLibraries(.NETFramework, v461, '', AnyCPU, '', '')" kann nicht ausgewertet werden. Der Versionszeichenfolgeteil war entweder zu kurz oder zu lang. C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets

   bei Microsoft.Build.Shared.ProjectErrorUtilities.ThrowInvalidProject(String errorSubCategoryResourceName, IElementLocation elementLocation, String resourceName, Object[] args)

   bei Microsoft.Build.Shared.ProjectErrorUtilities.VerifyThrowInvalidProject[T1,T2](Boolean condition, String errorSubCategoryResourceName, IElementLocation elementLocation, String resourceName, T1 arg0, T2 arg1)

   bei Microsoft.Build.Shared.ProjectErrorUtilities.ThrowInvalidProject[T1,T2](IElementLocation elementLocation, String resourceName, T1 arg0, T2 arg1)

   bei Microsoft.Build.Evaluation.Expander`2.Function`1.Execute(Object objectInstance, IPropertyProvider`1 properties, ExpanderOptions options, IElementLocation elementLocation)

   bei Microsoft.Build.Evaluation.Expander`2.PropertyExpander`1.ExpandPropertyBody(String propertyBody, Object propertyValue, IPropertyProvider`1 properties, ExpanderOptions options, IElementLocation elementLocation, UsedUninitializedProperties usedUninitializedProperties, IFileSystem fileSystem)

   bei Microsoft.Build.Evaluation.Expander`2.PropertyExpander`1.ExpandPropertiesLeaveTypedAndEscaped(String expression, IPropertyProvider`1 properties, ExpanderOptions options, IElementLocation elementLocation, UsedUninitializedProperties usedUninitializedProperties, IFileSystem fileSystem)

   bei Microsoft.Build.Evaluation.Expander`2.PropertyExpander`1.ExpandPropertiesLeaveEscaped(String expression, IPropertyProvider`1 properties, ExpanderOptions options, IElementLocation elementLocation, UsedUninitializedProperties usedUninitializedProperties, IFileSystem fileSystem)

   bei Microsoft.Build.Evaluation.Expander`2.ExpandIntoStringLeaveEscaped(String expression, ExpanderOptions options, IElementLocation elementLocation)

   bei Microsoft.Build.Evaluation.Evaluator`4.EvaluatePropertyElement(ProjectPropertyElement propertyElement)

   bei Microsoft.Build.Evaluation.Evaluator`4.EvaluatePropertyGroupElement(ProjectPropertyGroupElement propertyGroupElement)

   bei Microsoft.Build.Evaluation.Evaluator`4.PerformDepthFirstPass(ProjectRootElement currentProjectOrImport)

   bei Microsoft.Build.Evaluation.Evaluator`4.EvaluateImportElement(String directoryOfImportingFile, ProjectImportElement importElement)

   bei Microsoft.Build.Evaluation.Evaluator`4.PerformDepthFirstPass(ProjectRootElement currentProjectOrImport)

   bei Microsoft.Build.Evaluation.Evaluator`4.EvaluateImportElement(String directoryOfImportingFile, ProjectImportElement importElement)

   bei Microsoft.Build.Evaluation.Evaluator`4.PerformDepthFirstPass(ProjectRootElement currentProjectOrImport)

   bei Microsoft.Build.Evaluation.Evaluator`4.EvaluateImportElement(String directoryOfImportingFile, ProjectImportElement importElement)

   bei Microsoft.Build.Evaluation.Evaluator`4.PerformDepthFirstPass(ProjectRootElement currentProjectOrImport)

   bei Microsoft.Build.Evaluation.Evaluator`4.EvaluateImportElement(String directoryOfImportingFile, ProjectImportElement importElement)

   bei Microsoft.Build.Evaluation.Evaluator`4.PerformDepthFirstPass(ProjectRootElement currentProjectOrImport)

   bei Microsoft.Build.Evaluation.Evaluator`4.Evaluate(ILoggingService loggingService, BuildEventContext buildEventContext)

   bei Microsoft.Build.Evaluation.Evaluator`4.Evaluate(IEvaluatorData`4 data, ProjectRootElement root, ProjectLoadSettings loadSettings, Int32 maxNodeCount, PropertyDictionary`1 environmentProperties, ILoggingService loggingService, IItemFactory`2 itemFactory, IToolsetProvider toolsetProvider, ProjectRootElementCache projectRootElementCache, BuildEventContext buildEventContext, ISdkResolverService sdkResolverService, Int32 submissionId, EvaluationContext evaluationContext)

   bei Microsoft.Build.Evaluation.Project.Reevaluate(ILoggingService loggingServiceForEvaluation, ProjectLoadSettings loadSettings, EvaluationContext evaluationContext)

   bei Microsoft.Build.Evaluation.Project.ReevaluateIfNecessary(ILoggingService loggingServiceForEvaluation, ProjectLoadSettings loadSettings, EvaluationContext evaluationContext)

   bei Microsoft.Build.Evaluation.Project.Initialize(IDictionary`2 globalProperties, String toolsVersion, String subToolsetVersion, ProjectLoadSettings loadSettings, EvaluationContext evaluationContext)

   bei Microsoft.Build.Evaluation.Project..ctor(String projectFile, IDictionary`2 globalProperties, String toolsVersion, String subToolsetVersion, ProjectCollection projectCollection, ProjectLoadSettings loadSettings, EvaluationContext evaluationContext)

   bei Microsoft.VisualStudio.Build.ComInteropWrapper.ProjectShim.LoadProjectWithSettings(String projectFileName, ProjectLoadSettingsShim projectLoadSettings)

   bei EnvDTE.SolutionClass.AddFromFile(String FileName, Boolean Exclusive)

   bei Syncfusion.Templates.UI.VisualStudio.VsGenShell.<>c__DisplayClass17_0.<<AddProject>b__0>d.MoveNext()

--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---

   bei System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   bei Microsoft.VisualStudio.Threading.JoinableTask.CompleteOnCurrentThread()

   bei Syncfusion.Templates.UI.VisualStudio.VsGenShell.AddProject(String project)

   --- Ende der internen Ausnahmestapelüberwachung ---

   bei Syncfusion.Templates.UI.VisualStudio.VsGenShell.AddProject(String project)

   bei Syncfusion.Templates.UI.VisualStudio.VsGenShell.AddContextItemsToSolution(ProjectInfo projectInfo)

   bei Microsoft.Templates.Core.PostActions.Catalog.AddContextItemsToSolutionAndProjectPostAction.ExecuteInternal()

   bei Microsoft.Templates.Core.PostActions.PostAction.Execute()

   --- Ende der internen Ausnahmestapelüberwachung ---

   bei Microsoft.Templates.Core.PostActions.PostAction.Execute()

   bei Microsoft.Templates.Core.Gen.GenController.ExecuteGlobalPostActions()

   bei Microsoft.Templates.Core.Gen.GenController.<GenerateItemsAsync>d__4.MoveNext()

--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---

   bei System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   bei Microsoft.Templates.Core.Gen.NewProjectGenController.<UnsafeGenerateProjectAsync>d__4.MoveNext()

--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---

   bei System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   bei Syncfusion.Templates.UI.Services.GenerationService.<GenerateProjectAsync>d__5.MoveNext()

[Lothar Behrens]

Hi,

meanwhile I found some issues:

The target framework version v48 is missing the dot. Propably as well on different target framework settings.

The WinForms Template seems to be generating a WPF application, because it contains typical WPF code.

So, is the template somehow broken?

I think, that the target version string - for example v48 breaks further template creation stuff and thus the exception.

If I compare the VS 2017 example ribbon features, that Program.cs file did not using the following namespaces:

using Microsoft.Extensions.Configuration;

using Microsoft.Extensions.DependencyInjection;

using Microsoft.Extensions.Hosting;

I have attached a screenshot comparing the folders with the Program.cs opened on both.

Thanks,

Lothar

Attachment: 20240225_12_17_30Greenshot_e8fab02f.zip

[Kesavaraman Venkadesan]

Hi Lothar,

Query: Project creation with Template Studio fails

Response: We have reviewed the issue you reported regarding our WinForms Template Studio. Please refer to the details below for your query.

Root Cause: We were able to reproduce the issue when the selected framework version SDK is not installed. However, if the corresponding framework version is installed, the issue does not occur. Therefore, if the selected Framework SDK version is not installed, please install the specified .NET Framework version SDK on your machine and create the Syncfusion WinForms application using our template studio.

Workaround:

Verify whether the selected framework version is installed or not, please follow the below step:

Step1: Create a default Microsoft Windows Forms App (.NET Framework) project. In the framework combobox, you will find a list of installed framework versions. Verify if the selected framework version is present. If not, please follow the step 2 to install it.

Step 2:

        1. Search for Visual Studio Installer.

        2. Open Visual Studio Installer.

        3. Click on the "Modify" option for Visual Studio 2022.

 4. Choose "Individual components.

 5. Verify if the .NET framework version SDK is selected.

If the selected framework version is not chosen, select it, and click the "Modify" button at the bottom right to initiate the download if needed.

These steps will help you determine whether the chosen framework version is installed.

Step:3 When creating a Syncfusion WinForms template studio project with a specific framework version, if a pop-up window appears as shown in the attached image, click on the download option in the pop-up window.

Requesting Additional Information:

If the issue still persists, kindly provide a clear video demonstration  for further investigation. Also, please provide the following additional details:

1. In Visual Studio, go to Extensions -> Manage Extensions -> Installed and search for the Syncfusion extensions by providing the keyword “syncfusion" in the search box. Share the screenshot of that dialog.
2. In Visual Studio, go to Help > About Microsoft Visual Studio and click the Copy Info button. Then, paste the information into a text file and share it with us.
3. Gather log file. Please follow the steps in the link  to get the Gather log file.
   

Query: The target framework version v48 is missing the dot. Propably as well on different target framework settings.

Response: We have been unable to replicate this issue. When selecting the v4.8 framework, our Syncfusion WPF project was successfully created with v4.8 specified in the csproj file.

Can you please provide a complete video demonstration to reproduce the issue from our end?

Query:

The WinForms Template seems to be generating a WPF application, because it contains typical WPF code.

So, is the template somehow broken?

If I compare the VS 2017 example ribbon features, that Program.cs file did not using the following namespaces:

   using Microsoft.Extensions.Configuration;

   using Microsoft.Extensions.DependencyInjection;

   using Microsoft.Extensions.Hosting;

I have attached a screenshot comparing the folders with the Program.cs opened on both.

Response: Upon reviewing the attached screenshot, it's clear you're comparing our Syncfusion extension template with sample code. Our template is based on the default Microsoft WinForms template, hence the differences you observed. We've maintained a similar folder structure for both WPF and WinForms projects, with WinForms including respective designer files and WPF including XAML files. Regarding the namespaces you mentioned, those are provided in the Microsoft template, so we've included them in our syncfusion template as well.

Regards,

V. Kesavaraman