search

3F / DllExport

.NET DllExport with .NET Core support (aka 3F/DllExport aka DllExport.bat)
MIT License
961 stars 133 forks source link

Infinite loop when editing the solution #124

Closed vladkorotnev closed 4 years ago

vladkorotnev commented 4 years ago

Steps to reproduce:

  1. Create a solution with multiple projects and set the one that needs DllExport to depend on some other project
  2. Enable DllImport with DllImport.bat for one of them
  3. Close solution
  4. Reopen solution and delete some projects
  5. Close solution
  6. Reopen solution
  7. DllExport goes into an infinite loop of trying to build the dependency until your PC goes OOM
vladkorotnev commented 4 years ago

It also seems to force rebuild all projects whenever they are opened, which doesn't help if your solution contains a few heavy Rust projects

3F commented 4 years ago

Thanks for the report.

@vladkorotnev, What versions of VS and DllExport ?

DllExport goes into an infinite loop of trying to build the dependency

I'm trying even imagine this error but no result. Does exist some steps between 6 and 7?

By the way, what about msbuild? or it only when IDE? Or do you mean new configure when DllExport.bat?

Anyway, I was trying to test via 2 managed and 2 unmanaged projects in solution. The project dependency was added between the managed as Add - Reference.. - Projects, then as as you said. Nothing.

More probably something went wrong with your projects files/.sln and this is a VS issue. Can you also attach an mentioned files to inspect this? Or better some project template.

vladkorotnev commented 4 years ago

I'm using Visual Studio 2010, the managed project was C# and the unmanaged is VC++.

Initially I had 6 managed projects but then I split off the repositories and deleted 4 of them as well as all unmanaged ones. When I tried to open the solution, VS went into an infinite loop and crashed the OS.

When trying to launch the bat file with any arguments it was looping into MSBuild as follows -> ManagedDependencyProject (.../....DLL) -> ManagedDependencyProject (.../....DLL)

And so forth until I Ctrl-C out of it.

I'll try to make a minimal reproducible project and upload it when I get around to it.

3F commented 4 years ago

Sounds like corrupted/incorrect projects files(and/or .sln) as I already said above. Thus, you can also just attach the following files: .vcxproj, .csproj, and *.sln.

I'll try to make a minimal reproducible project

Thanks!

I'm using Visual Studio 2010,

In October 2016 Microsoft told me this ~

Our data shows that Visual Studio 2010 usage accounts for only a small single digit percentage of all Visual Studio usage

Well, after all this years, I'm still watching popularity of VS2010 for different users and organisations. See it?! That's why vsSolutionBuildEvent still provides support for it.

Btw I still have my personal boxed Pro version ^_^

3F commented 4 years ago

Closed due inactivity. Feel free to open it again.