UnitTestBoilerplateGenerator | Visual Studio that generates a unit test boilerplate | Unit Testing library
kandi X-RAY | UnitTestBoilerplateGenerator Summary
kandi X-RAY | UnitTestBoilerplateGenerator Summary
An extension for Visual Studio that generates a unit test boilerplate from a given class, setting up mocks for all dependencies. Supports NUnit, Visual Studio Test, XUnit and many mock frameworks.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of UnitTestBoilerplateGenerator
UnitTestBoilerplateGenerator Key Features
UnitTestBoilerplateGenerator Examples and Code Snippets
Community Discussions
Trending Discussions on UnitTestBoilerplateGenerator
QUESTION
I admit that I'm new to the world of xaml
but seeing warnings using the built-in Visual Studio templates indicate that there might be another issue besides my brain.
If I create an empty VSIX Project
(it has to be a VSIX Project) in Visual Studio using Add -> New Project
, and then proceed to create a new user control using Add -> New Item -> User Control (WPF)
, after I have compiled the code, the editor shows me the warning Ambiguous invocation
on the line InitializeComponent()
, as shown below:
There are warnings in the Designer view as well, shown below:
The warning is only present in the editor. Building the project is no problem, as shown below:
Please note that there are NO warnings if you add a User Control (WPF)
to a Class Library (.NET Framework)
project, as shown below:
If I look in the obj/Debug/
folder of SomeProject
I see two files for SomeControl
. The first is SomeControl.g.cs
, and the second is SomeControl.g.i.cs
. The files are identical.
The same goes for the obj/Debug/
folder of SomeOtherProject
, without the warning.
I have cloned various official Microsoft repos (e.g. UnitTestBoilerplateGenerator) and the warning is present here as well, for example in: src/View/CreateUnitTestBoilerplateDialog.xaml.cs at InitializeComponent()
, as shown below:
What's going on?? =(
EDITThis is using Visual Studio 15.4 and ReSharper 2017.2.2; I don't seem to be getting this warning with older versions of Visual Studio/ReSharper.
EDITThis seem to be a ReSharper specific problem, since after suspending ReSharper the warnings are no longer present. I have submitted a bug through ReSharper -> Help -> Report a Bug or Submit Feedback...
.
ANSWER
Answered 2018-Mar-05 at 11:26It is a known issue for ReSharper 2017.2.x
Update: It was fixed in ReSharper 2017.3 version.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install UnitTestBoilerplateGenerator
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page