Open gdurand opened 8 years ago
Hi, it's usually a bad idea to build a csproj outside of a solution context (e.g. nuget restores packages relative to solution directory, and solution configuration can alter configuration/platform for referenced projects), may I ask why you need to do it ?
That being said it'd be nice for this plugin not to crash in that scenario :)
In my solution, in Debug config, all the dependencies of my main project are built. For release I want only the main project to be built. I can achieve this by specifying only the main project in the Release config or create a "Debug Main" config, but I saw the option to build only 1 project in your plugin so I tried to use it. I can still work with the Release config and the solution. I just wanted to report a bug that is not so easy to figure out when first using the plugin. BTW I'm new to gradle and the integration of Visual Studio into an automated build system. I come from maven/java and things are quite not the same, to say the least.
This is actually fixed by #58 already, will be in vNext
I have this error when the build is configuring. If I specify a solution file it works fine and if I specifify a project file and remove the task assemblyInfoPatcher it works fine. The solution contains several projects. The project and solution are attached: project_and_solution.zip
The error (triggered by
com.ullink.AssemblyInfoVersionPatcher$_closure5.doCall
) :