devenv | CLI tool for managing several dev python environments

I am pretty new to Jmeter but can handle "simple" test plans. I really do need help with the issue I am facing. Currently I run into a problem regarding how to parametrize the Loop Controller loop count Groovy function.

I did found a lot of examples but they are all with static loop count like: ${__groovy(new File('test.csv').readLines().size(),)}. I really would like to parametrize the part 'test.csv'. Therefor I replaced that with ${csvFile}, like:

I work with Unity, and recently I came across some sort of bug with Visual Studio. For some reason one day the Script Editor stopped working.

When I first open it up through Unity, it would open as usual and seem fine, but after 5 seconds of interaction, Visual Studio would then freeze and crash without an error report. Following tries with the editor would just crash almost right away.

I did some research and found out that it was some sort of problem with Unity's MEF Cache, the Microsoft Documentation would ask me to do the following: Delete the following file: "%localappdata%\Microsoft\VisualStudio\ComponentModelCache" and if the problem continues, I should run this line of code on VS' CMD as a administrator "devenv /setup".

I tried both methods with Visual Studio, but neither seemed to work, only to return to being fine for 5 seconds before freezing and crashing.

I have updated Visual Studio 2017 to the newer version and performed the same method, but the problem persists.

I would like to know if anyone have any solutions to my situation, if I should try reinstalling Visual Studio, try to reinstall Unity or just use another Script Editor.

edit: Just to inform, the version of Unity I was using was 2021.2.8f1. But I don't know if it matters since the bug didn't seem to depend on the Unity version.

This only applies to Visual Studio 2022. I had uninstalled VS2019 and Preview where F# worked absolutely fine (F# 5.0). I am using VS2022 to use F# 6.0 and do not want to go back to F# 5.0.

The issue is specific to F#. I also use C# and I have no issues running the latest C# under VS2022.

There are near continual DevEnv processes running consuming anywhere from 1 to 4 of my CPU's 4 Hyperthreads. I have switched off all experimental options I can find in F# settings.

Sometimes there are 2 or more background processes running , sometimes paused and sometimes none - there appears to be no correlation between this and the background CPU consumption

Sometimes I have a pop up Dialog about waiting to complete an editor process or a compile process.

When devenev.exe is consuming CPU cycles under the properties I see there is always one clr.dllCoUnInitializeEE+0x6790 that is the culprit. I though this was meant to be a short-lived process? Sometimes there are two or three of these consuming most of a HyperThread (There are identical others but with very low or no CPU consumption). The stack on the guilty thread is as follows:

I'm trying to install conda environment using the command:

Sorry for a lengthy one, but I'm in dire straits - just trying to provide all details upfront.

This Fri (2021-Nov-12) after a restart of Visual Studio 2017 it began crashing without notice while opening existing solutions. This worked perfectly fine at least a week ago (after last Win10 Update KB5006670 on 2021-Nov-05 - followed by a reboot). Trying to load old solutions (which haven't been touched for 2+ years) results in exactly the same behavior:
you get a glimpse of "Loading Project .." windows (not sure if it goes through all projects in a solution), then suddenly the main VS window disappears and .. that's it.

VStudio's configuration has not been touched at least for a year. No explicit updates/patches or NuGet packages either. By itself VS starts and shows the main window with usual Start page. But I cannot load any solution or project.

The very first related Event Log entry:

So I must be doing something wrong. I created a new VSIX project following the wizard and just added the following two lines into the InitializeAsync method:

This question is related to How to code a utility msbuild project so that it depends on a "real" C# project?

So I have a working sample code where there is a utility project depending on a "real" C# project. It works fine when building on the console. Here are the files:

Currently trying to re-implement our build processes on our build server using MSBuild in place of devenv so that we don't need to have the full VS IDE installed. Having encountered quite a few issues with using MSBuild (race conditions, skipping shared resources instead of blocking, platform inconsistencies between parent and child, etc), I have settled upon building each project in separate tasks one by one to eliminate any concurrency issues and put /p:BuildProjectReferences=false in all the task command line fields to prevent MSBuild from imposing the platform of parent projects upon their heterogeneous children.

It seems however, that when I set this option to false as it is in devenv, MSBuild looks for the dependencies in the the top folder of the parent rather than in the bin as it should. e.g:

ProjectB depends on ProjectA

ProjectA has ..\bin\ProjectA.dll as output.

ProjectB references ProjectA as ..\bin\ProjectA.dll

C:\builds\solution\ProjectB\stdafx.cpp : fatal error C1192: #using failed on 'C:\builds\solution\ProjectB\ProjectA.dll'

Why does MSBuild check for dependency outputs in the parent project directory instead of the bin and what are the options to resolving this? Any insight is appreciated.

PS.

After some work I found a partial answer. For C++ I can disable the #using directive pointed at the parent project directory by setting Reference Assembly Output on the project reference in question to false, and then add the path to the Forced #using file field in the parent project configuration under C++ and advanced. This only works for C++ projects though. Still no idea what to do with C# projects.

It appears that MSBuild completely ignores /p:BuildProjectReferences=false when building a C# project, it then attempts to apply a x86 platform to its children, including C++ projects which have a Win32 platform in place of x86, which in turn somehow causes MSBuild to hunt for v100 (VS 2010) build tools that it won't find.

I have since learned a few things about the mechanism in MSBuild that governs this. Apparently there is a MSBuild task called AssignProjectConfiguration, which has a parameter labeled ShouldUnsetParentConfigurationAndPlatform. This is set to true in VS and false in MSBuild. It seems that this would be the source of the resulting configuration/platform mismatch. Why it builds dependencies despite my explicit command-line instructions not to and why the configuration/platform mismatch causes it to look for v100 VS 2010 build tools are both a mystery to me. I have a large log of verbose output to look through. I will endeavor to update this as I continue to read through the log.

I just changed a vcxproj file (C++) to have x86 as a platform for all solution build configurations instead of Win32, which seems to be the default for all C++ projects. The project loads fine but it shows up as a VS 2010 project in solution explorer. Based on discussions with my coworkers, my underlying assumption is that Win32 is identical to x86, but is an old tag for the platform, and that it would be better to remove it and replace it with x86. I have looked online for similar questions, and while I did find similar issues, the suggestions didn't seem to help.

The chain of events that prompted making this change is that we are currently starting an effort to modernize our software and processes, and part of this is to prepare for our build process eventually getting pushed onto a virtual machine as I set up a smoke test for the development team. Unfortunately, we have been using devenv.exe on an instance of CruiseControl.NET to do our installer builds; so, for the smoke test I have been tasked with getting MSBuild to work on our software so we can use that directly and not have the full VS IDE loaded on the VM.

To my horror, I have slowly learned over the last couple months that VS and MSBuild are not consistent with each other. MSBuild without the guiding hand of VS will not honor a build order, and so will often build projects and try to link it's dependencies before building the dependencies. It will also fail when projects try to access the same resource rather than just blocking. These problems together have brought me to break apart our build by project in our CCNet script instead of just building the solution file.

The place where the particular flavor of the problem in question stems from, is that MSBuild will look in the project references and attempt to build those dependencies with the parent project's configuration and platform super-imposed upon them. It seems that C# projects have x86 as their default platform while C++ has Win32. Our software is a C#/C++/CLI Frankenstein monster, and having inconsistent project platforms is wreaking havoc on my efforts. MSBuild also appears to always try building our x86 platform projects with 2010 build tools for some odd reason. This fails as we don't have those installed and we shouldn't have to.

I made these changes directly to the xml in a separate text editor by duplicating all the Win32 property groups, changing the platform on the copy to x86, saving the file, switching the configuration for all builds in VS to the new x86 platform, saving the solution, and then removing the old Win32 property groups. This appears to work but I now see the C++ project marked with "Visual Studio 2010", which explains to me why MSBuild keeps trying to use 2010 build tools, but what would be the purpose for this?

In short the question is this: why is VS loading x86 platform projects as 2010 projects? Any insight is appreciated, keeping in mind that we are wedded to VS as our IDE and MSBuild as our build program, and we want to still have our local devenv building work. Our C++/CLI code is all going to be rewritten to C# and we are moving from CCNet in the future, but we would like this to work with what we have right now.