You are viewing a plain text version of this content. The canonical link for it is here.
Posted to npanday-commits@incubator.apache.org by ap...@apache.org on 2010/09/16 01:55:47 UTC
svn commit: r997563 [2/3] - in /incubator/npanday/site: ./ src/ src/site/
src/site/apt/ src/site/apt/developers/ src/site/apt/developers/design/
src/site/apt/guide/ src/site/apt/guide/devinfra/
src/site/apt/guide/installation/ src/site/apt/guide/maven/...
Added: incubator/npanday/site/src/site/apt/guide/reference/supported-dir-structures.apt
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/apt/guide/reference/supported-dir-structures.apt?rev=997563&view=auto
==============================================================================
--- incubator/npanday/site/src/site/apt/guide/reference/supported-dir-structures.apt (added)
+++ incubator/npanday/site/src/site/apt/guide/reference/supported-dir-structures.apt Thu Sep 16 01:55:45 2010
@@ -0,0 +1,118 @@
+ ----
+ Supported Directory Structures
+ ----
+ ----
+
+Supported Directory Structures
+
+ The following directory structures are supported by NPanday's Visual Studio integration. Note that using the bare
+ Maven plugins you can support any directory structure, but it may require manual configuration of various plugin
+ fields.
+
+* Multi-module Projects
+
+ Multi-module project with a parent POM containing one or more modules, then a subdirectory for each module, which
+ equates to a VS "project". The <<<.sln>>> file sits beside the parent POM, and each subdirectory contains a
+ <<<.csproj>>>, <<<pom.xml>>> and source code. Source code is not typically put in a subdirectory under the module, but
+ it might be. NUnit test code may be within each module in a directory named "Tests", or it may be in a separate
+ module.
+
+----
+MySolution/
+|-- MyClassLibrary/
+| |-- Properties/
+| | `-- AssemblyInfo.cs
+| |-- Class1.cs
+| |-- MyClassLibrary.csproj
+| `-- pom.xml
+|-- MyClassLibraryTest/
+| |-- Properties/
+| | `-- AssemblyInfo.cs
+| |-- MyAppTest.cs
+| |-- MyClassLibraryTest.csproj
+| `-- pom.xml
+|-- MyConsoleApplication/
+| |-- Properties/
+| | `-- AssemblyInfo.cs
+| |-- MyConsoleApplication.csproj
+| |-- Program.cs
+| `-- pom.xml
+|-- MySolution.sln
+`-- pom.xml
+----
+
+* Flat Single Module Project
+
+ Flat structure with <<<pom.xml>>>, <<<.sln>>>, <<<.csproj>>> and source code all in the same directory. Source code is
+ not typically put in a subdirectory under the module, but it might be. If present, NUnit test code should be in a
+ directory named "Tests", which is not packaged in the main artifact. See note below about "nested" projects. The
+ "flat" structure is only supported as a single project with no sub-modules, for projects of type <<<library>>> (DLL)
+ and <<<exe>>>.
+
+----
+FlatSingleModule/
+|-- Properties/
+| `-- AssemblyInfo.cs
+|-- Class1.cs
+|-- FlatSingleModule.csproj
+|-- FlatSingleModule.sln
+`-- pom.xml
+----
+
+* Visual Studio Web Site Project
+
+ Visual Studio "Web Site" (File -> New -> Web Site) project with <<<.sln>>> file copied into the project directory and
+ modified to normalize paths. NPanday will build a zip file containing the aspx files and compiled dlls (in a bin/
+ directory). Note: There is an issue with building this type of project twice in a row: you must 'clean' before
+ building again.
+
+----
+MyWebSite
+|-- App_Data/
+|-- Default.aspx
+|-- Default.aspx.cs
+|-- MyWebSite.sln
+`-- pom.xml
+----
+
+* Visual Studio ASP.NET Web Application
+
+ Visual Studio "ASP.NET Web Application" (File -> New -> Project, "ASP.NET Web Application"). Structure is similar to
+ a multi-module project with a parent POM and <<<.sln>>> file at the top, plus a subdirectory for each project/module.
+ NPanday should build a .zip file as in the previous web site example containing pages and dlls.
+
+----
+MyProject/
+|-- MyWebApplication/
+| |-- Properties/
+| | `-- AssemblyInfo.cs
+| |-- Default.aspx
+| |-- Default.aspx.cs
+| |-- Default.aspx.designer.cs
+| |-- MyWebApplication.csproj
+| |-- Web.config
+| `-- pom.xml
+|-- MyProject.sln
+`-- pom.xml
+----
+
+ ~~TODO: ASP.NET Web Service Application
+
+ ~~TODO: ADO.NET project structure
+
+Notes
+
+ [[1]] Some versions of NPanday have limited support for a "nested" project-within-project structure with source code
+ in the parent directory. This structure will have a <<<.sln>>> <and> <<<.vbproj>>> file at the top, then
+ directories for additional modules beneath, each containing a <<<.vbproj>>> file. This structure is
+ <<not recommended>> and not likely to be fully supported by Maven tools such as the Release plugin
+
+ [[2]] In the examples, <<<.vbproj>>> and <<<.csproj>>> are interchangeable, each structure should work for any
+ language, and a solution may be composed of different modules using different languages. In addition, tests
+ within a module may be written in a different language than the main artifact
+
+ [[3]] The Visual Studio integration uses the project directory as the main directory for source code. However,
+ NPanday archetypes will generate projects using the more Maven-like convention of <<<src/main/csharp>>>, etc.
+
+ []
+
\ No newline at end of file
Added: incubator/npanday/site/src/site/apt/guide/reference/troubleshooting.apt
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/apt/guide/reference/troubleshooting.apt?rev=997563&view=auto
==============================================================================
--- incubator/npanday/site/src/site/apt/guide/reference/troubleshooting.apt (added)
+++ incubator/npanday/site/src/site/apt/guide/reference/troubleshooting.apt Thu Sep 16 01:55:45 2010
@@ -0,0 +1,118 @@
+ -----
+ Troubleshooting
+ -----
+ -----
+ 3 Feb 2010
+ -----
+
+Troubleshooting
+
+ If you encounter a problem with NPanday, try some of the following to resolve the issue before contacting the user
+ forums.
+
+* Check what version of NPanday you are currently using
+
+ The version can be viewed from the output console once you start NPanday
+
+[../../images/vs/console_version.jpg]
+
+ Another way to check for the version would be to go to <<Visual Studio Help \> About>> menu option
+
+[../../images/vs/vs_about.jpg]
+
+* Verifying Visual Studio 2005/2008 Service Pack 1 is installed
+
+ To make sure you have the Service Pack 1, go to <<Visual Studio Help \> About>> menu option. From the About screen,
+ verify that the Service Pack version is enclosed in parenthesis after the Visual Studio Version.
+
+ Another way to verify the Service Pack installation is to click <<Copy Info>> from the <<About>> screen and paste
+ the information in a text editor. Verify that the SP installation information is in the list.
+
+ For Visual Studio 2005
+
++------------------------------------------+
+Microsoft Visual Studio 2005 Professional
+Edition - ENU Service Pack 1 (KB926601)
++------------------------------------------+
+
+ For Visual Studio 2008
+
++-----------------------------+
+Microsoft Visual Studio 2008
+Version 9.0.30729.1 SP
+Microsoft .NET Framework
+Version 3.5 SP1
++-----------------------------+
+
+* Verifying .NET SDK installation
+
+ The SDK usually installs automatically when you install Visual Studio, but you might have to download it
+ separately and put it into the right place.
+
+** .NET 2.0 SDK (Visual Studio 2005)
+
+ To make sure you have the SDK, navigate to the following directory on your system: either in
+ <<<C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0>>> or <<<C:\Program Files\Microsoft.NET\SDK\v2.0>>>
+
+ Make sure the \v2.0 directory shown above contains all the pieces of the SDK (for example, the \Bin, \include,
+ \CompactFramework, and \Lib directories, among others).
+
+ <<Note>>: These are the default directories and it may be installed elsewhere on your system.
+
+ If the directory structure/folder shown above does not exist or is empty, download the SDK from the following
+ location: {{http://msdn2.microsoft.com/enus/downloads/default.aspx}}
+
+ <<Note>>: It is not necessary to move the SDK after you download it (for example, to the location where Visual Studio
+ puts it). Just make sure your PATH environment variable points to its location, as described in the PATH environment
+ variable prerequisite information, below.
+
+** .NET 3.5 SDK (Visual Studio 2008)
+
+ Verify that your system includes the following .NET Install Root directory:
+ <<<C:\WINDOWS\Microsoft.NET\Framework\v3.5>>>
+
+ <<Note>>: This directory should be in place by default from your Microsoft installation procedures.
+ If it is not, refer to the appropriate Microsoft documentation for help.
+
+** PATH
+
+ The PATH environment variable must be set such that it can find the following:
+
+ * The csc executable directory, the default path for which is: <<<C:\\WINDOWS\\Microsoft.NET\\Framework\\v3.5>>>
+ (or equivalent for .NET 2.0)
+
+ * The devenv executable directory, the default path is typically:
+ <<<C:\\Program Files\\Microsoft Visual Studio 9.0\\Common7\\IDE>>> (or equivalent for Visual Studio 2005)
+
+ []
+
+ Typically, the the <<<PATH>>> environment variable will look similar to this:
+
++------+
+PATH=%PATH%;C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE;C:\WINDOWS\Microsoft.NET\Framework\v3.5;
+C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;C:\Program Files\Microsoft Visual Studio 9\SDK\v3.5\bin;
+C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\bin
++------+
+
+ <<Note>>: To successfully install the NPanday add-in on machines with only Visual Studio 2008 installed, add this in
+ the PATH: <<<C:\\Program Files\\Microsoft SDKs\\Windows\\v6.0A\bin>>>.
+
+* Clearing the Visual Studio Add-in Cache
+
+ If you want to clear Visual Studio's cache of any previous versions of the tool before you start Visual Studio, run
+ the following command:
+
+----
+devenv /ResetAddin NPanday.VisualStudio.Addin
+----
+
+* Warnings when opening solutions generated by NPanday
+
+ Upon opening your Project/Solution, you may see a window with the selection <Load project normally>. This occurs
+ when you generate a Visual Studio solution from a Maven project (as opposed to importing the existing Solution in
+ Visual Studio).
+
+ Select that option and continue. This window may appear for each project, so select <Load project normally> each time,
+ or change the checkbox that indicates not to warn again.
+
+
Added: incubator/npanday/site/src/site/apt/guide/vs/assemblyKey.apt
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/apt/guide/vs/assemblyKey.apt?rev=997563&view=auto
==============================================================================
--- incubator/npanday/site/src/site/apt/guide/vs/assemblyKey.apt (added)
+++ incubator/npanday/site/src/site/apt/guide/vs/assemblyKey.apt Thu Sep 16 01:55:45 2010
@@ -0,0 +1,32 @@
+ ------
+ Setting Assembly Keys
+ ------
+ ------
+ 26 Feb 2009
+ ------
+
+Setting Assembly Keys
+
+ Assembly keys are used to uniquely identify the project to be installed in the Global Assembly Cache or also referred to as GAC.
+
+ To set an assembly key to a project, generate a strong name key by running the command
+
+----
+sn -k [filename] .snk
+----
+
+ Right click on the project and select <Set NPanday Compile Sign Assembly Key...>
+
+[../../images/vs/assembly_key.jpg]
+
+ Put the strong name key that was generated in the Assembly Sign Key field.
+
+[../../images/vs/set_assembly_key.jpg] Setting assembly sign key
+
+* Summary
+
+ We have now covered much of the functionality of NPanday Visual Studio Add-in. In subsequent sections of the guide,
+ we will examine the available configuration options.
+
+ The next topic is {{{./configureRepository.html} Configuring a Remote Repository}}, or you can return to the
+ {{{./index.html} index}}.
Added: incubator/npanday/site/src/site/apt/guide/vs/configureRepository.apt
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/apt/guide/vs/configureRepository.apt?rev=997563&view=auto
==============================================================================
--- incubator/npanday/site/src/site/apt/guide/vs/configureRepository.apt (added)
+++ incubator/npanday/site/src/site/apt/guide/vs/configureRepository.apt Thu Sep 16 01:55:45 2010
@@ -0,0 +1,74 @@
+ ------
+ Remote Repository Configuration
+ ------
+ ------
+ 26 Feb 2009
+ ------
+
+Remote Repository Configuration
+
+ A remote Maven repository can be configured using the Visual Studio IDE or it can be configured manually by adding
+ information to the Maven settings file.
+
+* Automatically Configure a Remote Maven Repository via the IDE
+
+ To access a remote Maven repository you can configure it from within Visual Studio. Visual Studio must be open,
+ the NPanday Build System must be running, and you must have a project loaded. Then:
+
+ [[1]] Right-click on a project and select Add Maven Artifact... from the menu.
+
+ [[2]] In the Add Maven Artifact pop-up window, click the Configure Repository tab.
+
+ [[3]] Select the URL of the repository in the pop-up window.
+
+ [[4]] If the remote repository allows snapshots or released artifacts to be stored there, then check the
+ appropriate box.
+
+ [[5]] Click Update. This will save the configuration to
+ <<<C:\\Documents and Settings\\[user_home]\\.m2\\settings.xml>>>. To edit multiple repositories, repeat
+ steps 3 to 5 by selecting another repository to be configured form the drop down list.
+
+ [[6]] Click Close when done configuring the repository.
+
+ []
+
+[../../images/vs/remote_repo.jpg] Sample configuration for Remote Repository
+
+ <<NOTE:>> The repository is stored in a profile NPanday.id this profile is then added into the activeProfiles list in
+ <<<settings.xml>>> as soon as an NPanday remote repository is added.
+
+* Manually Configure a Remote Maven Repository
+
+ To manually add a remote repository, add the following lines in your
+ <<<C:\\Documents and Settings\\[user_home]\\.m2\\settings.xml>>> file within the <<< \<profiles\> >>>
+ <<< \</profiles\> >>> tag. Modify the values for the <<< \<repository\> >>> and <<< \<id\> >>>elements
+ with the repository url you want to access.
+
++------+
+<profile>
+ <activation>
+ <activeByDefault>true</activeByDefault>
+ </activation>
+ <repositories>
+ <repository>
+ <releases>
+ <enabled>true</enabled>
+ </releases>
+ <snapshots>
+ <enabled>false</enabled>
+ </snapshots>
+ <id>http://repo1.maven.org/maven2/</id>
+ <url>http://repo1.maven.org/maven2/</url>
+ </repository>
+ </repositories>
+ <id>NPanday.id</id>
+</profile>
++------+
+
+ You should change the values of <<<enabled>>> for each of the artifact types, dependencing on whether the
+ repository contains that type of version.
+
+* Summary
+
+ The next configuration options are the {{{./settings.html} Maven settings}} themselves. You can also return to the
+ {{{./index.html} index}}.
Added: incubator/npanday/site/src/site/apt/guide/vs/executeGoals.apt
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/apt/guide/vs/executeGoals.apt?rev=997563&view=auto
==============================================================================
--- incubator/npanday/site/src/site/apt/guide/vs/executeGoals.apt (added)
+++ incubator/npanday/site/src/site/apt/guide/vs/executeGoals.apt Thu Sep 16 01:55:45 2010
@@ -0,0 +1,214 @@
+ ------
+ Executing Maven Goals
+ ------
+ ------
+ 26 Feb 2009
+ ------
+
+Executing Maven Goals
+
+ As we learned in the quick-start tutorial, it is possible to run Maven goals from within Visual Studio using NPanday.
+ This section explores the concept of the build lifecycle in more detail.
+
+* Compile
+
+ In the Solution Explorer, right-click on the name of the project you want to compile, then select
+ <<<Current NPanday Project \> Build>>> to build the selected project. Or, <<<All NPanday Projects \> Build>>> to build
+ the parent and its sub-projects.
+
+ <Note:> In some circumstances, Maven is currently unable to build (compile) without installing the project first. As a
+ workaround, execute <<<All NPanday Projects \> Install>>> first before <<<All NPanday Projects \> Build [compile]>>>.
+
+ For projects with dependencies from remote repositories, the build might fail. As a workaround, re-import the project
+ then, execute the build goal (<<<Current\ NPanday\ Project\ \>\ Build>>> or <<<All\ NPanday\ Projects\ \>\ Build>>>).
+
+ For projects with web references, a dialog box is prompted for updating the Web Services Description Language
+ (<<<wsdl>>>). Click Yes to continue with the update, or, No to skip updating.
+
+[../../images/vs/webservice_update.jpg]
+
+ The NPanday .NET Build Tool performs the compile on the project and sends corresponding information to the Output
+ window (including a message saying the build was successful). You can scroll up and down in the output window to
+ display all the text.
+
+ You can also execute the normal Visual Studio build on your projects. To invoke Maven to perform
+ <<<build>>>/<<<install>>>/<<<test>>>/<<<clean>>>, you must select the option from the All NPanday Projects or Current
+ NPanday Project sub-menu.
+
+ When compiling a web application project, the NPanday .NET Build Tool performs an extra step by calling the
+ <<<Aspnet_compiler>>> to validate the ASP section of the project. The Build Tool performs this step right after
+ calling the CSharp compiler and Visual Basic compiler.
+
+* Test
+
+ To use the NPanday .NET Build Tool to test a Project:
+
+ [[1]] From the Solution Explorer, right-click on the name of the project you want to test, then select
+ <<<Current NPanday Project \> Test>>> to perform the test to the selected project. Or,
+ <<<All NPanday Projects \> Test>>> to perform the test to the parent project and its sub-projects.
+
+ [[2]] The NPanday .NET Build Tool performs the tests on the project and sends corresponding information to the
+ Output window (including a message saying the build was successful). You can scroll up and down in the output
+ window to display all the text.
+
+ []
+
+ <<Note>>: When the test goal output result is not refreshed for C# test project, the project should be reimported, and
+ the value of the test should also be changed. Then, perform <<<Current\ Project:\ Test>>> (or,
+ <<<All NPanday Projects \> Test>>>).
+
+* Install
+
+ From the Solution Explorer, right-click on the name of the project you want to build, then select Current NPanday
+ Project > Install to install the selected project. Or, All NPanday Projects > Install to install the parent project
+ and its sub-projects.
+
+ The NPanday .NET Build Tool installs the artifacts into your local repository. For web projects with POM as packaging,
+ the <<<target>>> directory is not created and only the parent <<<pom.xml>>> is put in the local repository which is
+ the default behavior.
+
+ For web application projects, the project zip file is produced during this phase, specifically during the
+ <<<package>>> phase.
+
+ Corresponding information is sent to the Output window (including a message saying the build was successful).
+ You can scroll up and down in the output window to display all the text.
+
+ Next, verify the artifacts were placed into the .NET local repository under the following path:
+ <<< C:\\Documents and Settings\\[user_home]\\.m2\\uac\\[gac_architecture]\\artifactId\Version__GroupId >>>
+
+ For example:
+ <<< C:\\Documents and Settings\\[user_home]\\.m2\\uac\\gac_msil\\NPanday.Test\\1.0__NPanday >>>
+
+ The following explains what each element in the path means:
+
+ * <<<[user_home]>>> The user's home directory.
+
+ * <<<gac_architecture>>> The architecture type such as <<<gac_msil>>>, <<<gac_32>>>, etc.
+
+ * <<<artifactId>>> This is similar to the Maven <<<artifactId>>>. It is equivalent to the project's module name.
+ In the example above, the artifactId is <<<NPanday.Test>>>.
+
+ * <<<Version__GroupId>>> The version of the artifact and the group it is in.
+ In the example above the version is <<<1.0>>> and the GroupId is <<<NPanday>>>.
+
+ []
+
+ The contents in C:\\Documents and Settings\\[user_home]\\.m2\\uac\\gac_msil SHOULD NOT be manually modified or the
+ project build will fail due to artifacts that are not properly indexed and are not synchronized with the repository.
+ In case the contents have been modified, delete the C:\\Documents and Settings\\[user_home]\\.m2\\uac directory then
+ re-install the project.
+
+ Finally, Verify that the following are also created under the following paths:
+
+ * <<<C:\\Documents and Settings\\[user_home]\\.m2\\pab>>>
+
+ * <<<C:\\Documents and Settings\\[user_home]\\.m2\\npanday-settings.xml>>>
+
+ []
+
+ Contents of npanday-settings.xml looks similar to the following:
+
++------+
+ <?xml version="1.0" encoding="utf-8"?>
+ <npandaySettings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
+ <operatingSystem>
+ Microsoft Windows NT 5.1.2600 Service Pack 2
+ </operatingSystem>
+ <defaultSetup>
+ <vendorName>MICROSOFT</vendorName>
+ <vendorVersion>2.0.50727</vendorVersion>
+ <frameworkVersion>2.0.50727</frameworkVersion>
+ </defaultSetup>
+ <vendors>
+ <vendor>
+ <vendorName>MICROSOFT</vendorName>
+ <vendorVersion>1.1.4322</vendorVersion>
+ <frameworks>
+ <framework>
+ <frameworkVersion>1.1.4322</frameworkVersion>
+ <installRoot>
+ C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322
+ </installRoot>
+ </framework>
+ </frameworks>
+ </vendor>
+ <vendor>
+ <vendorName>MICROSOFT</vendorName>
+ <vendorVersion>2.0.50727</vendorVersion>
+ <frameworks>
+ <framework>
+ <frameworkVersion>2.0.50727</frameworkVersion>
+ <installRoot>
+ C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
+ </installRoot>
+ <sdkInstallRoot>
+ C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\
+ </sdkInstallRoot>
+ </framework>
+ </frameworks>
+ </vendor>
+ </vendors>
+ </npandaySettings>
++------+
+
+* Clean
+
+ To use the NPanday .NET Build Tool to clean a project (removes the <<<target\\ >>> directory containing the files that
+ were generated at build-time from the project's working directory):
+
+ [[1]] From the Solution Explorer, right-click on the name of the project you want to clean, then select Current
+ NPanday Project > Clean to clean the selected project. Or, All NPanday Projects > Clean to perform the clean
+ goal to the parent project and its sub-projects.
+
+ [[2]] The NPanday .NET Build Tool performs the clean on the project and sends corresponding information to the
+ Output window (including a message saying the build was successful). You can scroll up and down in the
+ output window to display all the text.
+
+ []
+
+* NPanday's Maven Phase Algorithm
+
+ Algorithm that differs the Visual Studio Execution from Console Command.
+
+ [[1]] All Project - Is triggered when the user right click in the solution explorer and select
+ <<<All NPanday Projects \> Build>>> or <<<All NPanday Projects \> Clean>>> or <<<All NPanday Projects \> Test>>>
+ or All NPanday Projects \> Install>>>
+
+ [[A]] Save All Documents that are open in Visual Studio.
+
+ [[B]] Retrieve the solution that is open in Visual Studio.
+
+ [[C]] Loop through all the projects in the solution.
+
+ [[D]] Check if it has a Web Reference, if it has it will update the Web Reference.
+
+ [[E]] Execute the pom.xml of the solution may it be Build/Clean/Test/Install.
+
+ []
+
+
+ [[2]] Current Project - Is Triggered when the user right click in the solution explorer and select
+ <<<Current NPanday Project \> Build>>> or <<<Current NPanday Project \> Clean>>> or
+ <<<Current NPanday Project \> Test>>> or <<<Current NPanday Project \> Install>>>
+
+ [[A]] Save All Documents that are open in Visual Studio.
+
+ [[B]] Retrieve CURRENT pom.xml and CURRENT project.
+
+ [[a]] If pom.xml does not exist, set errorMsg to "Pom Not Found" Error.
+
+ [[b]] If the packaging in the pom.xml is "pom", set errorMsg to "Pom may not be Project's Pom" Error.
+
+ []
+
+ [[C]] Check if it has a Web Reference, if it has it will update the Web Reference.
+
+ [[D]] Execute the pom.xml of the solution may it be Build/Clean/Test/Install.
+
+ []
+
+ []
+
+* Summary
+
+ Continue on to {{{./assemblyKey.html} Setting Assembly Keys}}, or return to the {{{./index.html} index}}.
\ No newline at end of file
Added: incubator/npanday/site/src/site/apt/guide/vs/importing.apt
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/apt/guide/vs/importing.apt?rev=997563&view=auto
==============================================================================
--- incubator/npanday/site/src/site/apt/guide/vs/importing.apt (added)
+++ incubator/npanday/site/src/site/apt/guide/vs/importing.apt Thu Sep 16 01:55:45 2010
@@ -0,0 +1,174 @@
+ ------
+ Importing Projects
+ ------
+ ------
+ 26 Feb 2009
+ ------
+
+Importing Projects
+
+ This section provides more details on how on importing a Visual Studio project using the
+ <Generate Solution's POM Information...> feature works. As we saw in the {{{./quickstart.html} Quickstart example}},
+ this feature will generate <<<pom.xml>>> files from an existing Visual Studio solution file. The generated
+ <<<pom.xml>>> file will contain the latest versions of the artifact dependencies used for the project.
+
+ <<Note>>: ASP.NET MVC should be installed to get the proper behavior when importing projects especially those projects
+ with unsupported project types. See {{{./importing.html#MVC} MVC projects}} for more details.
+
+ To import a project, first select <Generate Solution's POM Information...> from the project's context menu:
+
+[../../images/vs/generate-pom.jpg]
+
+ In the pop-up screen, Browse to the directory location of the parent solution file to use.
+
+ The <Group ID> is generated by default with the format of <<<[company_id].[solution_name]>>>.
+
+ The <SCM Tag> is optional. If you provide a url that is not reachable (e.g: it is authenticated and the credentials are not supplied or incorrect) by the Addin,
+ you will see a warning, but the url will still be added to the parent pom.
+
+[../../images/vs/import-dialog.jpg] Importing parent solution file
+
+ When you are ready, click <Generate POMs>.
+
+ Underscores and spaces in the artifact's Group ID are automatically deleted when added to the project's <<<pom.xml>>>.
+ The table below shows the conversion of certain values of groupIds.
+
+*------------------------+------------------------+
+| <<Artifact Group Id>> | <<Converted Group Id>> |
+*------------------------+------------------------+
+|The.Project |The.Project |
+*------------------------+------------------------+
+|the.project |the.project |
+*------------------------+------------------------+
+|the project |TheProject |
+*------------------------+------------------------+
+|the_project |TheProject |
+*------------------------+------------------------+
+
+ Next, the project unit tests window will appear. If you have modules that are for unit tests only, select them and
+ click OK.
+
+[../../images/vs/unit-tests.JPG] Project unit tests list
+
+ <<<pom.xml>>> files will be generated for all the projects that are included in the solution file, including the
+ parent project and its sub-projects, if there are any.
+
+ <<Note>>: The Units Tests window is not displayed when importing unsupported project types. Hence, an unsupported
+ project type warning is displayed. For multi-module projects with supported and/or unsupported project types, the
+ supported projects are included in the parent POM while for the unsupported project types, these are not included
+ in the parent POM, and a warning is displayed.
+
+ For projects with web references, the <<<pom.xml>>> generated will contain <<<maven-wsdl-plugin>>> configuration
+ similar to the following:
+
++------+
+ <plugin>
+ <groupId>npanday.plugin</groupId>
+ <artifactId>maven-wsdl-plugin</artifactId>
+ <extensions>true</extensions>
+ <executions>
+ <execution>
+ <goals>
+ <goal>wsdl</goal>
+ </goals>
+ </execution>
+ </executions>
+ <configuration>
+ <webreferences>
+ <webreference>
+ <namespace>AnotherWebService</namespace>
+ <path>Web References/AnotherWebService/AnotherWS.wsdl</path>
+ <output>Web References/AnotherWebService/</output>
+ </webreference>
+ </webreferences>
+ </configuration>
+ </plugin>
++------+
+
+ The wsdl goal is the one responsible for building and creating webservice proxy classes. And, all the web references
+ used in the project are listed inside the <<< \<webreferences\> >>> tag. For more instructions on adding, renaming,
+ and deleting web references, refer to {{{./webReferences.html} Web References}} section of this guide.
+
+ Other project types will generate corresponding plugins needed to build that type of project (for example, the compile
+ plugin, aspx plugin, or msbuild plugin).
+
+* Importing Projects with Resource Files
+
+ If the project you are importing includes a resource file, the <<<maven-resgen>>> plugin is added to <<<pom.xml>>>
+ during import.
+
+ In the plugin's configuration, you can find the list of resource (<<<resx>>>) files with corresponding names.
+ By default, <<<RootNamespace>>> is the assembly name and <<<RootNamespace.Filename>>> is the filename of the
+ <<<resx>>> files.
+
+ To ensure that the plugin works, the following are required:
+
+ * The classname and the filename of the item that contains the resx files must have the same name. Example:
+ <<<"public class frmMaestroName" = frmMaestroName.resx = frmMaestroName.cs>>>
+
+ <<Note>>: Changing the codefile(.cs/.vb) automatically updates the resource(resx) file. In some instances,
+ however, this does not hold true.
+
+ * The namespace of the project should be equal to the DefaultNamespace of the project assembly. To check the default
+ name,
+
+ * Right-click on the project and select Properties. This displays a project property window.
+
+ * Select the Application tab.
+
+ * In the DefaultNamespace field, you will find <<<RootNamespace>>>.
+
+ []
+
+ []
+
+ Once the above requirements are met, the importer automatically does the work and there is no need to edit
+ <<<pom.xml>>>.
+
+ Removing the configuration part of the <<<maven-resgen>>> plugin allows the plugin to locate all the resx files and
+ compile them as <<<ArtifactId.Filename>>>. If you set the namespace as the artifactId, you do not need to list all the
+ resx files in the <<<pom.xml>>>.
+
+ <<Note>>: This feature does not support cultured esx files such as <<<eu-US>>>, <<<it>>>, <<<jp>>>, <<<de>>>,
+ <<<eu-UK>>>, and even custom culture.
+
+* Importing WPF/WCF Projects with XAML files
+
+ If the project you are Importing is a WPF/WCF project and it contains a XAML file the MSBuildPlugin will be
+ automatically added into that project's pom file.
+
++------+
+ <plugin>
+ <groupId>npanday.plugin</groupId>
+ <artifactId>NPanday.Plugin.Msbuild.JavaBinding</artifactId>
+ <executions>
+ <execution>
+ <goals>
+ <goal>compile</goal>
+ </goals>
+ </execution>
+ </executions>
+ </plugin>
++------+
+
+ This will generate the needed *.g.cs/*.g.vb files that are needed for those XAML files.
+
+ <<Note:>> The user would encounter double dependency errors, if the project was created with 3.0 .NET framework. We
+ suggest that you change your framework to 3.5 and then delete the references that are already included as defaults in
+ NPanday. This will then allow your project to run successfully.
+
+* Importing ASP.NET {MVC} Projects
+
+ As of NPanday 1.1, MVC projects are not support for import as Maven projects from the Visual Studio Add-in.
+ However, in some situations they may be incorrectly imported as a normal C# or VB project.
+
+ To avoid this problem, make sure you have installed ASP.NET MVC Release Candidate 2 which can be obtained from
+ {{http://www.microsoft.com/downloads/details.aspx?FamilyID=ee4b2e97-8a72-449a-82d2-2f720d421031&displaylang=en}}.
+
+ This must be installed to skip the unsupported project types and be able to get the correct project type GUID.
+
+* Summary
+
+ This section has described how to import a project, and the nuances of various different supported project types.
+
+ You can now read on about {{{./executeGoals.html} executing Maven goals}}, or go back to the {{{./index.html} index}}.
Added: incubator/npanday/site/src/site/apt/guide/vs/index.apt
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/apt/guide/vs/index.apt?rev=997563&view=auto
==============================================================================
--- incubator/npanday/site/src/site/apt/guide/vs/index.apt (added)
+++ incubator/npanday/site/src/site/apt/guide/vs/index.apt Thu Sep 16 01:55:45 2010
@@ -0,0 +1,57 @@
+ ----
+ Using the NPanday Visual Studio Add-in
+ ----
+ ----
+ 3 February 2010
+ ----
+
+Using the NPanday Visual Studio Add-in
+
+ By this point, you should have NPanday successfully installed as shown in the
+ {{{../installation/index.html} Installation instructions}}, and have Visual Studio started with the NPanday Build Tool
+ running.
+
+ This guide will walk you through a basic introduction to the Visual Studio Add-in, how to use it for typical project
+ tasks, and what configuration options are available.
+
+ Finally, we will discuss the use cases where you might need to manipulate the Maven POM directly and other advanced
+ use cases.
+
+ After completing this guide, you may want to read the guide to
+ {{{../devinfra/index.html} Using NPanday with your Maven Development Infrastructure}}.
+
+ If you encounter any problems, don't forget to consult the
+ {{{../reference/troubleshooting.html} Troubleshooting guide}}.
+
+* Contents
+
+~~ TODO: add testing?
+
+ * {{{./quickstart.html} Quick Start Guide}} - starting a new project and making it buildable by Maven
+
+ * {{{./references.html} Working with references}} - how adding references impacts the project, and how it works with
+ Maven depedencies
+
+ * {{{./webReferences.html} Working with web references}} - how web references in a web application work with NPanday
+
+ * {{{./resyncReferences.html} Keeping references in sync}} - how to ensure project files are portable and references
+ are always available
+
+ * {{{./importing.html} Creating Maven POM's from Visual Studio projects}} - more detail on the import process covered
+ in the quick start guide, including different project types supported
+
+ * {{{./executeGoals.html} Executing Maven Goals}} - more detail on the integration of the Maven lifecycle with
+ Visual Studio by the NPanday Add-in
+
+ * {{{./assemblyKey.html} Setting the Assembly Key}} - how to set a strong name on your build using NPanday
+
+ * {{{./configureRepository.html} Configuring a Remote Repository}} - the steps necessary to have a remote repository
+ for downloading Maven artifacts from
+
+ * {{{./settings.html} Maven settings}} - how to configure an alternate Maven settings file
+
+ * {{{../maven/releasing.html} Releasing .NET projects with Maven}} - how to use the Maven release mechanism from the
+ command line
+
+ []
+
\ No newline at end of file
Added: incubator/npanday/site/src/site/apt/guide/vs/quickstart.apt
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/apt/guide/vs/quickstart.apt?rev=997563&view=auto
==============================================================================
--- incubator/npanday/site/src/site/apt/guide/vs/quickstart.apt (added)
+++ incubator/npanday/site/src/site/apt/guide/vs/quickstart.apt Thu Sep 16 01:55:45 2010
@@ -0,0 +1,282 @@
+ ------
+ Quick Start Guide
+ ------
+ ------
+ 26 Feb 2009
+ ------
+
+Quick Start Guide
+
+ This section is provides a quick overview of the NPanday .NET Build Tool by creating a sample project. You must first
+ have installed the Add-in according to the instructions in the {{{../installation/index.html} installation guide}}.
+
+* Starting the Add-in
+
+ Start Visual Studio ensuring that your PATH is set correctly, as described in the installation guide.
+
+ Next, in Visual Studio start the NPanday Build System from Tools>NPanday Build System. You will see NPanday starting
+ in the Visual Studio Output pane.
+
+ <Note:> After you start the NPanday Build System and it is running, it no longer appears as an option on the Tools
+ menu (and reappears again when Visual Studio is stopped and started). Therefore, if you had previously started
+ the NPanday Build System and it is still running, you do not need to start it again in this step.
+
+* Creating a Project
+
+ Creating a project for use with NPanday is the same as you would normally do so for any project within Visual Studio.
+ In this case, we will create a class library.
+
+ [[1]] Got to File > New > Project...
+
+ [[2]] Retain the default of a C# Class Library (if you are using a different language variant of the IDE that will
+ also work)
+
+ [[3]] In the <Name> field, type <<<NPandayTestQS>>>
+
+ [[4]] Keep the other options the same (using the same name for the Solution and creating a directory for the
+ solution) and press OK.
+
+ []
+
+ You now have a simple, standard, project. However, nothing has been generated for Maven to be able to build it, so
+ for that we need to generate a <<<pom.xml>>> file.
+
+* Generating the POM
+
+ NPanday makes creating the POM file(s) easy. To do so, right click on the project solution (or any of the projects)
+ in the Solution Explorer and select <Generate Solution's POM Information...>:
+
+[../../images/vs/generate-pom.jpg]
+
+ Next, you will see the following dialog:
+
+[../../images/vs/import-dialog.jpg]
+
+ We'll look at this in more detail shortly, but for now accept the default settings, and do likewise on the next dialog
+ asking about test projects. Finally, NPanday will inform you that it has created two <<<pom.xml>>> files: one for the
+ solution, and one for the class library project. These files won't appear in the Solution Explorer - NPanday keeps
+ them hidden as they don't need to be modified directly. However, they should be checked into your source control
+ system to ensure that they can be used by other developers and the shared build infrastructure. In the next section we
+ will take a closer look at the POM files.
+
+** About the POM file
+
+ First, we need to understand what the <<<pom.xml>>> file is. This is the sole descriptor used by Maven to build an
+ entire project. In some respects, it is similar to the <<<.sln>>> and <<<.csproj>>> (or <<<.vbproj>>>) files, however
+ Maven uses a different approach - while these are 'scripts', the POM is 'declarative', indicating where parts of the
+ project are located, and which Maven plugins are used to build the project, utilizing that project information. By
+ being declarative in this fashion, many plugins can operate on the same information without having to reconfigure
+ each specifically.
+
+ Let's look at POM for the solution first:
+
+----
+<?xml version="1.0" encoding="utf-8"?>
+<project xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ xmlns="http://maven.apache.org/POM/4.0.0">
+ <modelVersion>4.0.0</modelVersion>
+ <groupId>MyCompany.NPandayTestQS</groupId>
+ <artifactId>NPandayTestQS-parent</artifactId>
+ <packaging>pom</packaging>
+ <name>MyCompany.NPandayTestQS : NPandayTestQS-parent</name>
+ <version>1.0-SNAPSHOT</version>
+ <modules>
+ <module>NPandayTestQS</module>
+ </modules>
+</project>
+----
+
+ You will notice a few important elements here. First, there is the <Group ID> which is the value that you entered into
+ the previous dialog. There is also an <Artifact ID> that is the name of the solution with 'parent' appended. Further
+ down, there is a <Version> that is set to the default of <<<1.0-SNAPSHOT>>>. These 3 elements constitute the project
+ <co-ordinate>, which is a unique identifier across all projects you can access to this particular project. This is
+ the reason that the solution appends <<<-parent>>> to the end, to distinguish it from the child project with the same
+ name.
+
+ Within the group/artifact ID combination, each project is then versioned to distinguish between different
+ releases. The default is <<<1.0-SNAPSHOT>>>, which means "in development towards the 1.0 release". Maven places
+ special significance on the <<<SNAPSHOT>>> addition to a version, which means that the project is changing. When a
+ version is set to a concrete one such as <<<1.0>>>, Maven considers it to always remain the same and changes to go
+ under a new version (such as <<<1.1-SNAPSHOT>>>).
+
+ We will later use these co-ordinates to locate and utilize dependencies on other projects from within our own project,
+ even if we don't have a copy locally.
+
+ We also see the <Modules> section that shows which subproject exist. This contains a reference to the class library's
+ project directory - so let's now look at the POM for that:
+
+----
+<?xml version="1.0" encoding="utf-8"?>
+<project xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ xmlns="http://maven.apache.org/POM/4.0.0">
+ <parent>
+ <artifactId>NPandayTestQS-parent</artifactId>
+ <groupId>MyCompany.NPandayTestQS</groupId>
+ <version>1.0-SNAPSHOT</version>
+ <relativePath>..\pom.xml</relativePath>
+ </parent>
+ <modelVersion>4.0.0</modelVersion>
+ <artifactId>NPandayTestQS</artifactId>
+ <packaging>library</packaging>
+ <name>MyCompany.NPandayTestQS : NPandayTestQS</name>
+ <build>
+ <sourceDirectory>./</sourceDirectory>
+ <plugins>
+ <plugin>
+ <groupId>npanday.plugin</groupId>
+ <artifactId>maven-compile-plugin</artifactId>
+ <extensions>true</extensions>
+ <configuration>
+ <frameworkVersion>2.0.50727</frameworkVersion>
+ <includeSources>
+ <includeSource>Class1.cs</includeSource>
+ <includeSource>Properties\AssemblyInfo.cs</includeSource>
+ </includeSources>
+ </configuration>
+ </plugin>
+ </plugins>
+ </build>
+</project>
+----
+
+ This project starts with the <Parent> definition, which points back to the project for the solution. This is used to
+ inherit any shared settings among subprojects (though by default, there is nothing saved in the parent POM that will
+ be shared).
+
+ Next we have the artifact ID for this project, which uses the library name. The group ID and version can be omitted,
+ since by default they will use the same one as the parent project.
+
+ In this project, we have altered the <Packaging> element to be of type <<<library>>>. While the parent was a
+ <<<pom>>>, indicating it didn't build anything additional, this type indicates that Maven and NPanday should include
+ all the standard build steps for a .NET class library.
+
+ Along with this we now have a <Build> section. This contains two further elements - first, the <source directory>,
+ that says the Visual Studio convention of storing source files in the project directory (and subdirectories) will be
+ followed. Next is the <Plugins> section, which is where Maven is told to use NPanday to compile, and what framework
+ and source code to use. For other project types, additional plugins may be added (see the
+ {{{../../plugins/index.html} Plugins Reference}} for more available plugins).
+
+ While it is not necessary to be able to create these POM files to be able to use NPanday, understanding how they work,
+ and in particular the Maven co-ordinate system, will help to understand what NPanday is doing "behind the scenes"
+ when you use some of its other functionality.
+
+* Building the Project
+
+ With this in place, we can now check that Maven is able to build the project. Right click on the solution or project
+ and select <All NPanday Projects>, then <Build [compile]>.
+
+[../../images/vs/build.png]
+
+ In the Output Window (if the NPanday Execution Output view is selected from the dropdown), you will see something
+ similar to the following:
+
++---+
+------------------------------------------------------------------
+Executing Maven
+Pom File: C:\...\Visual Studio 2008\Projects\NPandayTestQS\pom.xml
+Goal: compile
+Arguments: compile
+NPanday Command: c:\...\apache-maven-2.2.1\bin\mvn.bat compile
+
+
+------------------------------------------------------------------
+
+[INFO] Scanning for projects...
+[INFO] Reactor build order:
+[INFO] MyCompany.NPandayTestQS : NPandayTestQS-parent
+[INFO] MyCompany.NPandayTestQS : NPandayTestQS
+[INFO] ------------------------------------------------------------------------
+[INFO] Building MyCompany.NPandayTestQS : NPandayTestQS-parent
+[INFO] task-segment: [compile]
+[INFO] ------------------------------------------------------------------------
+[INFO] No goals needed for project - skipping
+[INFO] ------------------------------------------------------------------------
+[INFO] Building MyCompany.NPandayTestQS : NPandayTestQS
+[INFO] task-segment: [compile]
+[INFO] ------------------------------------------------------------------------
+[INFO] [compile:initialize {execution: default-initialize}]
+...
+[INFO] [resolver:resolve {execution: default-resolve}]
+...
+[INFO] [NPanday.Plugin.Settings.JavaBinding:generate-settings {execution: default-generate-settings}]
+[INFO] [compile:generate-assembly-info {execution: default-generate-assembly-info}]
+...
+[INFO] [compile:process-sources {execution: default-process-sources}]
+...
+[INFO] [compile:process-test-sources {execution: default-process-test-sources}]
+...
+[INFO] [resgen:copy-resources {execution: default-copy-resources}]
+[INFO] [resgen:generate {execution: default-generate}]
+[INFO] [resgen:generate-existing-resx-to-resource {execution: default-generate-existing-resx-to-resource}]
+[INFO] [compile:compile {execution: default-compile}]
+...
+[INFO]
+[INFO] ------------------------------------------------------------------------
+[INFO] Reactor Summary:
+[INFO] ------------------------------------------------------------------------
+[INFO] MyCompany.NPandayTestQS : NPandayTestQS-parent ........ SUCCESS [0.005s]
+[INFO] MyCompany.NPandayTestQS : NPandayTestQS ............... SUCCESS [10.547s]
+[INFO] ------------------------------------------------------------------------
+[INFO] ------------------------------------------------------------------------
+[INFO] BUILD SUCCESSFUL
+[INFO] ------------------------------------------------------------------------
+[INFO] Total time: 18 seconds
+[INFO] Finished at: Wed Feb 03 12:58:47 EST 2010
+[INFO] Final Memory: 12M/24M
+[INFO] ------------------------------------------------------------------------
+NPanday Execution is Successful!
++---+
+
+ Here, both projects are built (since it was run from the solution level). The solution POM has no steps to perform to
+ compile. However, you can see several steps (<<<compile:initialize>>>, <<<resolver:resolve>>>, and so on) performed
+ for the library. These are all defined by the POM's <<<packaging>>> element.
+
+ Of course, the existing built-in commands are still available for building from Visual Studio, so development need not
+ change day to day - but the build is there to be sure that the POM works as expected, so that you have the same build
+ as other systems that will use it.
+
+ You may have noticed that there were other options that <Build> - namely <Test>, <Install> and <Clean>. There are
+ other parts of what is known as the Maven <Build Lifecycle>.
+
+** The Build Lifecycle
+
+ Maven uses the POM to drive builds that a constructed as <patterns>. No matter what type of project you are building
+ it can be shaped to Maven's build lifecycle, which is a sequence of phases always run in the same order, and for which
+ a given phase can be sure that the previous phases have always executed as part of this build.
+
+ There are quite a number of phases that Maven plugins can participate, and that you can run from the <<<mvn>>>
+ command, but the Visual Studio Add-in exposes the primary ones:
+
+ * <<<compile>>> - compile source code into binary output
+
+ * <<<test>>> - run unit tests (such as NUnit) against the code to verify that the package will work
+
+ * <<<install>>> - produce the package and install it into Maven's <local repository>.
+
+ What this means is that if you run <<<mvn install>>>, you will actually run compile, then test, then install (and
+ the intermediate steps). Maven views testing as important, so this structure ensures that you run any unit tests
+ you have before using the final DLL, for example. Running the <install> phase is the most common one used when building
+ a project with Maven.
+
+ The installation phase is different to the traditional meaning of installing software. Maven maintains a <local
+ repository> on the current machine (by default in <<<%HOMEDRIVE%%HOMEPATH%\\.m2\\repository>>>) where all build output
+ is stored. This common storage allows sharing between different projects on the same machine when they express a
+ dependency on another project. You have already encountered this when installing NPanday, as Maven uses the local
+ repository to house it's own functionality as well.
+
+ We'll also learn later that Maven utilizes <remote repositories> to obtain dependencies from other sources, and to
+ publish build output for sharing with other users. In this case, the local repository acts as a local intermediatary
+ and cache between Maven and the remote repositories.
+
+ In addition to the above phase, there is the <Clean> option, which uses a different 'lifecycle' for cleaning up any
+ build output such as the <<<target>>>, <<<Bin>>> and <<<Obj>>> directories.
+
+* Summary
+
+ In this simple example, we've seen how we can turn an existing .NET project into a functional Maven project, and
+ learned some of the basic terminology and interactions with the new build system. In further parts of the guide,
+ we will learn more about how Visual Studio and Maven interact through NPanday.
+
+ You can now read on about {{{./references.html} working with references}}, or go back to the {{{./index.html} index}}.
+
+
Added: incubator/npanday/site/src/site/apt/guide/vs/references.apt
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/apt/guide/vs/references.apt?rev=997563&view=auto
==============================================================================
--- incubator/npanday/site/src/site/apt/guide/vs/references.apt (added)
+++ incubator/npanday/site/src/site/apt/guide/vs/references.apt Thu Sep 16 01:55:45 2010
@@ -0,0 +1,162 @@
+ ------
+ Project Dependencies
+ ------
+ ------
+ 26 Feb 2009
+ ------
+
+~~TODO convert to example style with a working example like NUnit, rather than this reference style (or perhaps put that in the QS guide?)
+
+Project Dependencies
+
+ This feature allows the Visual Studio user to browse managed repositories and add and delete Maven dependencies to and
+ from the repositories from within the Visual Studio IDE.
+
+ A remote repository must be configured before attempting to use this feature. Please see the
+ {{{./configureRepository.html} Remote Repository}} section for instructions.
+
+ <<Note>>: Adding dependencies should be done using Visual Studio while manually adding is not recommended. At this
+ time, the Visual Studio add-in will not detect changes to the Maven dependencies and add them to your Visual Studio
+ project. If you manually add a dependency and re-import the project in Visual Studio, the recently added dependencies
+ are deleted from the <<<pom.xml>>> file.
+
+* Adding Maven Artifacts
+
+ Adding a Maven artifact allows you to refer to a DLL or other dependency that may not yet be installed on the local
+ machine. This is done by consulting a Maven <remote repository> for available dependencies, and adding a reference
+ to the Maven <<<pom.xml>>>.
+
+ When adding an artifact dependency into a web site project, there will be no changes in the <<<pom.xml>>>. This is
+ because the artifacts are put directly into the project's <<<bin\\>>> directory (one is created when this is missing),
+ thus, <<< \<dependencies\> >>> in the <<<pom.xml>>> is not needed.
+
+ To add an artifact:
+
+ [[1]] Right-click on a project and select Add Maven Artifact... from the menu.
+
+ [[2]] In the Add Maven Artifact pop-up window there are tabs for each repository you have configured.
+ Click the tab for the repository in which the desired artifact is located.
+
+ [[3]] Scroll to select the desired artifact (must be a <<<DLL>>> file, not a <<<JAR>>> nor an <<<OCX>>> file):
+
+ [[4]] Click Add to add the selected artifact and exit the form. Or, double click on the artifact to be added.
+ Repeat this step to add multiple artifacts. Then, click Close to exit the form.
+
+ []
+
+[../../images/vs/add_artifact.jpg] Add Maven Artifact screen
+
+ The artifacts will be added as a reference to the project and added as a dependency in the POM file. It is
+ also downloaded to the <<<C:\\Documents and Settings\\[user_home]\\.m2\\uac>>> directory.
+
+** COM References
+
+ When attempting to add an <<<.ocx>>> file into the repository, a warning message similar to the following will be
+ displayed:
+
+[../../images/vs/com_reference.jpg] COM reference error message
+
+ See below for adding COM references directly.
+
+** .NET References
+
+ As of version 1.2 when adding .NET References NPanday will no longer add system scope and system path properties on the
+ .NET dependency.
+
+* Adding References
+
+ You can also add traditional references to the project and have NPanday translate them into Maven dependencies.
+
+ To add references to the project:
+
+ [[1]] Right click on the project that you want to add a reference to.
+
+ [[2]] Select Add Reference... from the menu list.
+
+ [[3]] Select the tab to which the reference belongs (<<.NET>>, <<COM>>, <<Projects>>). Or, Browse to look for the
+ specific artifact to be reference and Recent for artifacts recently accessed.
+
+ [[4]] Select the references to be added from the list as shown in the figure above. Scroll to select the desired object reference.
+
+ [[5]] Click OK.
+
+ []
+
+[../../images/vs/references_list.jpg] Sample display of list of references
+
+ NPanday will take care of adding the reference to the Maven POM automatically. In most cases this will also be made
+ available on any other system building from the Maven project. In the case of an inter-project dependency, it will
+ rely on the project being built on the target machine before the project that has the dependency on it - but all that
+ is needed here is to build the whole solution as Maven will then take care of the correct ordering.
+
+ However, some references are non-portable when they are added.
+
+** Intra Solution References
+
+ When Adding Intra Solution references use the Visual Studio "Add Reference" and not the "Add Maven Artifact" command.
+ This sets the csproj/vbproj file & the pom.xml correctly simultaenously, and allows VS to build the project without
+ needing to resolve the reference.
+
+** Non-portable References
+
+ When adding a COM reference, the actual reference (DLL) is copied to <<<C:\\WINDOWS\\assembly\\GAC_MSIL>>>.
+ Wherein, the path to the reference found in this directory is used as the reference's <<< \<systemPath\> >>> in the
+ <<<pom.xml>>>. References such as this rely on the given DLL being available at the same location on each machine.
+
+ When adding an artifact reference that is not installed in the system, NPanday will prompt a warning
+ message then adds the reference in the <<<pom.xml>>> as a system scope dependency.
+
+[../../images/vs/dependency_error.jpg] Reference not installed in the system
+
+ However, the above warning message is not displayed for web site projects even if the artifact reference to be added
+ is not installed in the system. This is because the artifact references for web projects are directly added in the project's
+ <<<bin\\>>> directory (one is created when this is missing), thus, no need to add it in the <<<pom.xml>>>.
+
+ The following POM snippet shows a system dependency:
+
++------+
+ <dependency>
+ <groupId>artifact_group_id</groupId>
+ <artifactId>my.lib</artifactId>
+ <version>2.2</version>
+ <type>library</type>
+ <scope>system</scope>
+ <systemPath>C:\path\to\your\library.dll</systemPath>
+ </dependency>
++------+
+
+* Removing Artifacts and References
+
+ The Remove Artifact feature removes the artifact as a reference to the project and as a dependency in the POM file.
+
+ To remove an artifact, you can select the artifacts to remove and click the Delete key. This works for both Visual
+ Basic and C# projects.
+
+ Alternatively, to remove Visual Basic project artifact:
+
+ [[1]] Right-click on a project and select Properties from the menu.
+
+ [[2]] Click on the References tab, and select the desired artifact.
+
+ [[3]] Click Remove.
+
+ []
+
+ Alternatively, to remove C# project artifact:
+
+ [[1]] Inside the project, browse through the References folder.
+
+ [[2]] Right click on the desired artifact and select Remove.
+
+ []
+
+* Summary
+
+ This has covered all options for adding one of Maven's most powerful features - dependency resolution - to your
+ .NET projects by using NPanday.
+
+ The next section continues with {{{./webReferences.html} web references}}. You can also go back to the
+ {{{./index.html} index}}.
+
+ In the next section we revisit {{{./importing.html} importing a project into Maven}}. Other topics are available on
+ the {{{./index.html} index}}.
Added: incubator/npanday/site/src/site/apt/guide/vs/resyncReferences.apt
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/apt/guide/vs/resyncReferences.apt?rev=997563&view=auto
==============================================================================
--- incubator/npanday/site/src/site/apt/guide/vs/resyncReferences.apt (added)
+++ incubator/npanday/site/src/site/apt/guide/vs/resyncReferences.apt Thu Sep 16 01:55:45 2010
@@ -0,0 +1,33 @@
+ ------
+ Making VS Project Files Portable
+ ------
+ ------
+ 22 April 2009
+ ------
+
+Making VS Project Files Portable
+
+ To be able to make VS project files portable, NPanday 1.1 and above provides the Resync References functionality.
+ This will synchronize the references so that the project will still run in other user's machine. Added references
+ will be stored in hidden folder named ".references". When the project is used in other user's machine, the Resync
+ References functionality will download and store the references in the ".references" folder.
+
+ To use Resync References button, right click on the project and go to 'All NPanday Projects' or 'Current NPanday
+ Project' in the context menu and select 'Resync References'.
+
+ Intra-project references are skipped on Resync. Since this behavior was just applied recently in Version 1.0.2,
+ old POMs with intra-project references might generate an error during Resync or Import. To fix this, remove the
+ reference and add it back again. Or simply delete the POM and re-import the project.
+
+ How Resync Works:
+
+ * First NPanday will check for the dependency in the local repository, if the dependency is not found NPanday proceeds
+ to the next possible location.
+
+ * If NPanday was not able to find the dependency in the local repository NPanday will proceed to check the remote
+ repositories found in the user's settings.xml.
+
+ * For SNAPSHOT Dependencies NPanday bases from the maven-metadata.xml and gets the latest time stamp versioned dependency.
+
+ In the next section we revisit {{{./importing.html} importing a project into Maven}}. Other topics are available on
+ the {{{./index.html} index}}.
Added: incubator/npanday/site/src/site/apt/guide/vs/settings.apt
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/apt/guide/vs/settings.apt?rev=997563&view=auto
==============================================================================
--- incubator/npanday/site/src/site/apt/guide/vs/settings.apt (added)
+++ incubator/npanday/site/src/site/apt/guide/vs/settings.apt Thu Sep 16 01:55:45 2010
@@ -0,0 +1,24 @@
+ ------
+ Using Custom Settings
+ ------
+ ------
+ 26 Feb 2009
+ ------
+
+Using Custom Settings
+
+ This feature allows the Visual Studio user to customize the location of the <<<settings.xml>>> file that points to the
+ repository of NPanday artifacts.
+
+ To change the location, right click on the project and select the <Change Maven settings.xml...>
+
+[../../images/vs/change_settings.jpg]
+
+ In the pop-up screen, click Browse to browse through the directory location of the <<<settings.xml>>> to use.
+
+[../../images/vs/settings_location.jpg] Configure settings.xml location
+
+* Summary
+
+ This concludes the configuration section of the guide. Return to the {{{./index.html} index}}.
+
Added: incubator/npanday/site/src/site/apt/guide/vs/webReferences.apt
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/apt/guide/vs/webReferences.apt?rev=997563&view=auto
==============================================================================
--- incubator/npanday/site/src/site/apt/guide/vs/webReferences.apt (added)
+++ incubator/npanday/site/src/site/apt/guide/vs/webReferences.apt Thu Sep 16 01:55:45 2010
@@ -0,0 +1,59 @@
+ ------
+ Web References
+ ------
+ ------
+ 26 Feb 2009
+ ------
+
+Web References
+
+ Web references are artifacts that refer to the web service. These are usually in web format.
+
+ The following procedures in adding, renaming, and deleting web references assumes that the project in which the web
+ references will be added, renamed, or deleted has an existing <<<pom.xml>>> file from a previous import. Executing the
+ following procedures will also make changes to the <<<pom.xml>>> file of the project.
+
+ Luckily these procedures are identical to normal Visual Studio development.
+
+* Adding Web References
+
+ [[1]] Right click on the project that you want to add a web reference to.
+
+ [[2]] Select Add Web Reference... from the menu list.
+
+ [[3]] Select the web service you want to add, or you can choose to type the URL.
+
+ [[4]] Supply a Name for the reference. This will be used to call the reference later in your code.
+
+ []
+
+[../../images/vs/web-reference.png]
+
+* Renaming Web References
+
+ [[1]] Right click on the web reference of the project application that you want to rename. Or, right click on the folder containing the
+ wsdl file of the web service of the web project that you want to rename.
+
+ [[2]] Select Rename.
+
+ [[3]] Supply the new Name for the reference. This will be used to call the reference later in your code.
+
+ []
+
+* Removing Web References
+
+ [[1]] Right click on the web reference of the project application that you want to delete. Or, right click on the folder where
+ the wsdl file of the web service of the web project that you want to delete.
+
+ [[2]] Select Delete.
+
+ []
+
+* Summary
+
+ As you can see, working with web references is very familiar - all of the procedures are the same, with the
+ <<<pom.xml>>> changes handled by NPanday behind the scenes. You may, out of interest, want to review the POM after
+ the addition of a web reference.
+
+ Having understood references, the next topic is maintaining them across different checkouts in the document
+ {{{./resyncReferences.html} making project files portable}}. You can also return to the {{{./index.html} index}}.
Added: incubator/npanday/site/src/site/apt/index.apt
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/apt/index.apt?rev=997563&view=auto
==============================================================================
--- incubator/npanday/site/src/site/apt/index.apt (added)
+++ incubator/npanday/site/src/site/apt/index.apt Thu Sep 16 01:55:45 2010
@@ -0,0 +1,88 @@
+ ------
+ NPanday Overview
+ ------
+ ------
+ 24 Feb 2009
+ ------
+
+NPanday
+
+ NPanday is a project to integrate {{{http://maven.apache.org} Apache Maven}} into .NET development environments.
+ It includes both a Visual Studio add-in to integrate Maven, and a set of {{{./plugins/}plugins}} for Maven
+ that can build .NET projects uniformly from the command line.
+
+ NPanday enables you to use Visual Studio with a Maven-based development infrastructure, including:
+
+ * continuous integration servers for scheduled or triggered automated builds
+
+ * source control systems for assistance with the release process
+
+ * build artifact repositories for inter-project dependency management and centralised management of build output
+
+ You can read more about {{{http://maven.apache.org/maven-features.html} Maven's features}} on the Maven
+ web site.
+
+ NPanday doesn't intend to replicate MSBuild's (or Visual Studio's build) behavior exactly, or necessarily serve as
+ a replacement for Visual Studio users, but rather to:
+
+ * augment Visual Studio with dependency management and make the build reproducible in clean environments
+
+ * offer a consistent toolchain to build environments with projects in other languages (particularly those using Maven for Java projects)
+
+ * offer a solution for declarative builds for .NET projects that will work consistently whether Visual Studio is used or not
+
+ * expose other Maven features and plugins to .NET projects
+
+ []
+
+ For more information about NPanday, refer to the following guides:
+
+ * {{{./features.html} Features}}
+
+ * {{{./faqs.html} FAQs}}
+
+ * {{{./release-notes.html} Release Notes}}
+
+* User's Guide
+
+ * {{{./guide/index.html} Introduction}}
+
+ * {{{./guide/installation/index.html} Installation}}
+
+ * {{{./guide/vs/index.html} Visual Studio Add-In User's Guide}}
+
+ * {{{./guide/maven/index.html} Maven Command Line User's Guide}}
+
+ * {{{./guide/devinfra/index.html} Using with Maven-based Development Infrastructure}}
+
+ * {{{./plugins/index.html} Maven Plugin Reference}}
+
+* Contributing to NPanday
+
+ NPanday is an open source project under the Apache License 2.0. You are free to use the application and source code as
+ you wish under those terms.
+
+ We welcome you to contribute to the project by submitting your requests and feedback, patches to the code and
+ participating in development discussions in the discussion area.
+
+ We are looking for active contributors to join the project, and use the Apache meritocracy model by nominating and
+ voting for committers from those that regularly discuss development and submit patches for fixes and enhancements.
+
+** Developer's Guide
+
+ The {{{./developers/index.html} NPanday developer's guide}} contains information on how to checkout and build NPanday
+ for yourself, debug issues, and contribute fixes. It also covers committer's procedures such as the release process
+ and publishing documentation.
+
+** Reporting Bugs and Requesting Features
+
+ You can also help by contributing high quality bug reports and feature requests via the issue tracker, and questions
+ and ideas via the discussion forums:
+
+ * {{{./issue-tracking.html} issue tracking}}
+
+ * {{{./mail-lists.html} mailing list information}}
+
+Documentation PDF
+
+ This documentation is also available in a {{{./npanday.pdf} single pdf}}.
Added: incubator/npanday/site/src/site/index.html
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/index.html?rev=997563&view=auto
==============================================================================
--- incubator/npanday/site/src/site/index.html (added)
+++ incubator/npanday/site/src/site/index.html Thu Sep 16 01:55:45 2010
@@ -0,0 +1,51 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<h1>NPanday</h1>
+
+<p>
+</p>
+
+
+<h2>About NPanday</h2>
+<p>
+ NPanday primarily provides two capabilities: a set of Maven plugins, for constructing builds in Maven that use the .NET command-line tools; and a Visual Studio Addin that keeps a Visual Studio project in sync with the Maven POM and adds reference resolution from Maven artifact repositories. Together this allows you to use a single tool across .NET, Java or any other Maven-based projects, including the same benefits of dependency management, automated release and source control management, and so on.
+ </p>
+</div>
+
+
+<h2>News</h2>
+<div>
+<p>
+08 September 2010: <a href="http://npanday.codeplex.com/releases/view/47408">Release 1.2.1 available.</a>
+This is our 8th release, incorporating many bug fixes, improved documentation, greatly enhanced the performance on projects with many (transitive) dependencies and a variety of new features, including code coverage for Java and .Net modules.
+</p>
+</div>
+
+
+<h2>Getting Started </h2>
+<div>
+<p>
+ Releases are available on the <a href="http://npanday.codeplex.com/releases/view/47408"> Downloads Page </a>. For documentation, check <a href="http://www.npanday.org/docs/1.2/index.html">here</a>.
+ </p>
+</div>
+
+
+<h2> Getting Involved </h2>
+<div>
+<p>
+ NPanday is an open source project under the Apache License 2.0. You are free to use the application and source code as you wish under those terms.
+
+We welcome you to contribute to the project by submitting your requests and feedback, patches to the code and participating in development discussions in the discussion area.
+
+We are looking for active contributors to join the project, and use the Apache meritocracy model by nominating and voting for committers from those that regularly discuss development and submit patches for fixes and enhancements.
+ </p>
+</div>
+
+
+<div>
+ Copyright ©
+ 2008 <a href="http://www.apache.org/licenses/">The Apache Software Foundation.</a>
+</div>
+</body>
+</html>
Added: incubator/npanday/site/src/site/resources/css/site.css
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/css/site.css?rev=997563&view=auto
==============================================================================
--- incubator/npanday/site/src/site/resources/css/site.css (added)
+++ incubator/npanday/site/src/site/resources/css/site.css Thu Sep 16 01:55:45 2010
@@ -0,0 +1,4 @@
+#banner {
+/* background-color: rgb(166, 140, 125);*/
+ background-color: white;
+}
Added: incubator/npanday/site/src/site/resources/images/NPanday.png
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/NPanday.png?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/NPanday.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/Thumbs.db
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/Thumbs.db?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/Thumbs.db
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/developers/design/PluginDesign.png
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/developers/design/PluginDesign.png?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/developers/design/PluginDesign.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/developers/design/Thumbs.db
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/developers/design/Thumbs.db?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/developers/design/Thumbs.db
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/logo-home.png
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/logo-home.png?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/logo-home.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/Thumbs.db
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/Thumbs.db?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/Thumbs.db
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/add_artifact.jpg
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/add_artifact.jpg?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/add_artifact.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/assembly_key.jpg
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/assembly_key.jpg?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/assembly_key.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/build.png
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/build.png?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/build.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/change_settings.jpg
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/change_settings.jpg?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/change_settings.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/com_reference.jpg
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/com_reference.jpg?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/com_reference.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/console_version.JPG
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/console_version.JPG?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/console_version.JPG
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/dependency_error.jpg
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/dependency_error.jpg?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/dependency_error.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/generate-pom.jpg
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/generate-pom.jpg?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/generate-pom.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/import-dialog.jpg
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/import-dialog.jpg?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/import-dialog.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/installer/Thumbs.db
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/installer/Thumbs.db?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/installer/Thumbs.db
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/installer/screen1.jpg
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/installer/screen1.jpg?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/installer/screen1.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/installer/screen2.jpg
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/installer/screen2.jpg?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/installer/screen2.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/installer/screen3.jpg
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/installer/screen3.jpg?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/installer/screen3.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/installer/screen4.jpg
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/installer/screen4.jpg?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/installer/screen4.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/installer/screen5.jpg
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/installer/screen5.jpg?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/installer/screen5.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/installer/verify_installation.jpg
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/installer/verify_installation.jpg?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/installer/verify_installation.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/references_list.jpg
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/references_list.jpg?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/references_list.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/remote_repo.jpg
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/remote_repo.jpg?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/remote_repo.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/set_assembly_key.jpg
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/set_assembly_key.jpg?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/set_assembly_key.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/settings_location.jpg
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/settings_location.jpg?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/settings_location.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/unit-tests.JPG
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/unit-tests.JPG?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/unit-tests.JPG
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/vs_about.JPG
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/vs_about.JPG?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/vs_about.JPG
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/web-reference.png
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/web-reference.png?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/web-reference.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Added: incubator/npanday/site/src/site/resources/images/vs/webservice_update.jpg
URL: http://svn.apache.org/viewvc/incubator/npanday/site/src/site/resources/images/vs/webservice_update.jpg?rev=997563&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/npanday/site/src/site/resources/images/vs/webservice_update.jpg
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream