# Build breaking change in version 7.0.0.2671 action->Build VS.net solution

**URL:** https://www.finalbuilder.com/forums/t/build-breaking-change-in-version-7-0-0-2671-action-gt-build-vs-net-solution/3526
**Category:** Bugs
**Created:** [April 9, 2014, 11:26am UTC](https://www.finalbuilder.com/forums/t/build-breaking-change-in-version-7-0-0-2671-action-gt-build-vs-net-solution/3526 "2014-04-09T11:26:31Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![jom\_widex](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/j/4af34b/32.png) [@jom\_widex](https://www.finalbuilder.com/forums/u/jom_widex)
#### Post date: [April 9, 2014, 11:26am UTC](https://www.finalbuilder.com/forums/t/build-breaking-change-in-version-7-0-0-2671-action-gt-build-vs-net-solution/3526/1 "2014-04-09T11:26:31Z")

</div>

finalbbuilder7&nbsp;version 7.0.0.2671

.net 4.5.1

action: Build&nbsp;VS.net solution

set to: vs.net 2012, use msBuild = true, action=build, use RegEx in configName=false, Fail Action if no configuration match=false

**issue** configuration.

Preveiously it was ok have "configuration=Release" i.e partly specified.

after update to 2671 builds now longer compiles the solution, the action is "green" but the message shows: No configurations matched the value [Release]

Compile is restored with: ""configuration=Release|Win32"

**Problem:**

**The alterations is a braeking change. Historic builds will fail. This problem could have been avoided, with a check box like: StrictEval with a default value of false, allowing the actions previous behaviour to persist.**

&nbsp;

&nbsp;

---

<div class="post-metadata">

### Author: ![nevar](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/n/c4cdca/32.png) [@nevar](https://www.finalbuilder.com/forums/u/nevar)
#### Post date: [April 10, 2014, 12:49pm UTC](https://www.finalbuilder.com/forums/t/build-breaking-change-in-version-7-0-0-2671-action-gt-build-vs-net-solution/3526/2 "2014-04-10T12:49:48Z")

</div>

Hi O2m,   
  
The following build has a fix for this error. The previous change was only meant to warn the user that a configuration wasn’t found, it was still meant to allow building of the solution. The build can be downloaded here:   
  
[http://downloads.finalbuilder.com/downloads/finalbuilder/700/FB700\_2777.exe](http://downloads.finalbuilder.com/downloads/finalbuilder/700/FB700_2777.exe)