Copy Page

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account. You can also Sign Up for a new account.

<ul>
	<li>For each of the available dotnet archetypes:
	<ul>
		<li>Create a project from the archetype</li>
		<li>Build the project at the command line</li>
		<li>Generate a solution for the project</li>
		<li>Open the solution in Visual Studio and build the project using the VS Addin</li>
	</ul>
	</li>
</ul>

<ul>
	<li>Import (generate poms) and then build each of the projects in sandbox/dotnet-examples using the VS Addin
	<ul>
		<li>The 'flat' ones won't generate a correct pom at the moment.</li>
	</ul>
	</li>
</ul>

<ul>
	<li>Build each of the projects in sandbox/dotnet-examples/with-pom at the command line</li>
</ul>

<ul>
	<li>Generate solutions for each of the projects in sandbox/dotnet-examples/with-pom and try them in VS</li>
</ul>

<ul>
	<li>Verify that a failing NUnit test fails the build, and that ignoring failures is configurable</li>
</ul>

<ul>
	<li>Introduce a dependency on a snapshot artifact that is available in a remote repo, and build the project</li>
</ul>

<ul>
	<li>Introduce a &lt;parent&gt; element to a project and build again.
	<ul>
		<li>Try with both a snapshot and a released parent</li>
		<li>Try with the parent pom being retrieved from a remote repository</li>
	</ul>
	</li>
</ul>

<ul>
	<li>Try all of the VS Addin features at least once
	<ul>
		<li>Import a project (generate poms)</li>
		<li>Add NMaven Artifact (does it add to the solution file also?)</li>
		<li>Add Reference (does it add to the pom?  should it?  (Framework dependencies shouldn't be in the pom.))</li>
		<li>Remove NMaven Artifact (does it remove from the solution? does it remove anything it shouldn't?)  (... does this menu option still exist or do we just use Remove Reference?)</li>
		<li>Remove Reference (does it remove from the pom?)</li>
	</ul>
	</li>
</ul>

<ul>
	<li>Make sure that the solution/project files and pom files stay in sync for all the possible actions you can take within Visual Studio
	<ul>
		<li>Adding a dependency</li>
		<li>Changing the version number</li>
		<li>...</li>
	</ul>
	</li>
</ul>

<p>Note:  Delete your local repository, pab and uab directories frequently to test that artifacts can be resolved from a remote repo.</p>

<p>TODO:  Compare generated solutions &amp; poms with expected/golden files</p>