-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updating externals to NTS v2.11 / GeoAPI v2.11a and adding initial an…
…d incomplete Cairo renderer work. If you get latest and it does not build try force updating GeoAPI and possibly NTS deleting the directories and re-downloading if necessary. You may also need to build the NTS solution before building the SharpMap solution
- Loading branch information
Showing
24 changed files
with
2,990 additions
and
14 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| using SharpMap.Presentation.AspNet.Demo.NoCache; | ||
| using SharpMap.Rendering.Web.Cairo; | ||
|
|
||
| namespace SharpMap.Presentation.AspNet.Demo.Cairo | ||
| { | ||
| public class DemoCairoMapHandler : DemoMapHandler | ||
| { | ||
| protected override IWebMapRenderer CreateMapRenderer() | ||
| { | ||
| return new CairoImageRenderer(); | ||
| } | ||
| } | ||
| } |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| <%@ WebHandler Language="C#" Class="SharpMap.Presentation.AspNet.Demo.Cairo.DemoCairoMapHandler" %> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
Binary file not shown.
136 changes: 136 additions & 0 deletions
136
SharpMap.Rendering/Cairo/SharpMap.Rendering.Cairo.Tests/AuthoringTests.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,136 @@ | ||
| ========================================================================== | ||
| Visual Studio Team System: Overview of Authoring and Running Tests | ||
| ========================================================================== | ||
|
|
||
| This overview describes the features for authoring and running tests in | ||
| Visual Studio Team System and Visual Studio Team Edition for Software Testers. | ||
|
|
||
| Opening Tests | ||
| ------------- | ||
| To open a test, open a test project or a test metadata file (a file with | ||
| extension .vsmdi) that contains the definition of the test. You can find | ||
| test projects and metadata files in Solution Explorer. | ||
|
|
||
| Viewing Tests | ||
| ------------- | ||
| To see which tests are available to you, open the Test View window. Or, | ||
| if you have installed Team Edition for Software Testers, you can also open | ||
| the Test List Editor window to view tests. | ||
|
|
||
| To open the Test View window, click the Test menu, point to Windows, and | ||
| then click Test View. To open the Test List Editor window (if you have | ||
| installed Team Edition for Software Testers), click Test, point to Windows, | ||
| and then click Test List Editor. | ||
|
|
||
| Running Tests | ||
| ------------- | ||
| You can run tests from the Test View window and the Test List Editor window. | ||
| See Viewing Tests to learn how to open these windows. To run one or more | ||
| tests displayed in the Test View window, first select the tests in that | ||
| window; to select multiple tests, hold either the Shift or CTRL key while | ||
| clicking tests. Then click the Run Tests button in the Test View window | ||
| toolbar. | ||
|
|
||
| If you have installed Visual Studio Team Edition for Software Testers, you can | ||
| also use the Test List Editor window to run tests. To run tests in Test List Editor, | ||
| select the check box next to each test that you want to run. Then click the | ||
| Run Tests button in the Test List Editor window toolbar. | ||
|
|
||
| Viewing Test Results | ||
| -------------------- | ||
| When you run a test or a series of tests, the results of the test run will be | ||
| shown in the Test Results window. Each individual test in the run is shown on | ||
| a separate line so that you can see its status. The window contains an | ||
| embedded status bar in the top half of the window that provides you with | ||
| summary details of the complete test run. | ||
|
|
||
| To see more detailed results for a particular test result, double-click it in | ||
| the Test Results window. This opens a window that provides more information | ||
| about the particular test result, such as any specific error messages returned | ||
| by the test. | ||
|
|
||
| Changing the way that tests are run | ||
| ----------------------------------- | ||
| Each time you run one or more tests, a collection of settings is used to | ||
| determine how those tests are run. These settings are contained in a “test | ||
| run configuration” file. | ||
|
|
||
| Here is a partial list of the changes you can make with a test run | ||
| configuration file: | ||
|
|
||
| - Change the naming scheme for each test run. | ||
| - Change the test controller that the tests are run on so that you can run | ||
| tests remotely. | ||
| - Gather code coverage data for the code being tested so that you can see | ||
| which lines of code are covered by your tests. | ||
| - Enable and disable test deployment. | ||
| - Specify additional files to deploy before tests are run. | ||
| - Select a different host, ASP.NET, for running ASP.NET unit tests. | ||
| - Select a different host, the smart device test host, for running smart device unit tests. | ||
| - Set various properties for the test agents that run your tests. | ||
| - Run custom scripts at the start and end of each test run so that you can | ||
| set up the test environment exactly as required each time tests are run. | ||
| - Set time limits for tests and test runs. | ||
| - Set the browser mix and the number of times to repeat Web tests in the | ||
| test run. | ||
|
|
||
| By default, a test run configuration file is created whenever you create a | ||
| new test project. You make changes to this file by double-clicking it in | ||
| Solution Explorer and then changing its settings. (Test run configuration | ||
| files have the extension .testrunconfig.) | ||
|
|
||
| A solution can contain multiple test run configuration files. Only one of | ||
| those files, known as the “Active” test run configuration file, is used to | ||
| determine the settings that are currently used for test runs. You select | ||
| the active test run configuration by clicking Select Active Test Run | ||
| Configuration on the Test menu. | ||
|
|
||
| ------------------------------------------------------------------------------- | ||
|
|
||
| Test Types | ||
| ---------- | ||
| Using Visual Studio Team Edition for Software Testers, you can create a number | ||
| of different test types: | ||
|
|
||
| Unit test: Use a unit test to create a programmatic test in C++, Visual C# or | ||
| Visual Basic that exercises source code. A unit test calls the methods of a | ||
| class, passing suitable parameters, and verifies that the returned value is | ||
| what you expect. | ||
| There are three specialized variants of unit tests: | ||
| - Data-driven unit tests are created when you configure a unit test to be | ||
| called repeatedly for each row of a data source. The data from each row | ||
| is used by the unit test as input data. | ||
| - ASP.NET unit tests are unit tests that exercise code in an ASP.NET Web | ||
| application. | ||
| - Smart device unit tests are unit tests that are deployed to a smart device | ||
| or emulator and then executed by the smart device test host. | ||
|
|
||
| Web Test: Web tests consist of an ordered series of HTTP requests that you | ||
| record in a browser session using Microsoft Internet Explorer. You can have | ||
| the test report specific details about the pages or sites it requests, such | ||
| as whether a particular page contains a specified string. | ||
|
|
||
| Load Test: You use a load test to encapsulate non-manual tests, such as | ||
| unit, Web, and generic tests, and then run them simultaneously by using | ||
| virtual users. Running these tests under load generates test results, | ||
| including performance and other counters, in tables and in graphs. | ||
|
|
||
| Generic test: A generic test is an existing program wrapped to function as a | ||
| test in Visual Studio. The following are examples of tests or programs that | ||
| you can turn into generic tests: | ||
| - An existing test that uses process exit codes to communicate whether the | ||
| test passed or failed. 0 indicates passing and any other value indicates | ||
| a failure. | ||
| - A general program to obtain specific functionality during a test scenario. | ||
| - A test or program that uses a special XML file (called a “summary results | ||
| file”), to communicate detailed results. | ||
|
|
||
| Manual test: The manual test type is used when the test tasks are to be | ||
| completed by a test engineer as opposed to an automated script. | ||
|
|
||
| Ordered test: Use an ordered test to execute a set of tests in an order you | ||
| specify. | ||
|
|
||
| ------------------------------------------------------------------------------- | ||
|
|
||
|
|
35 changes: 35 additions & 0 deletions
35
SharpMap.Rendering/Cairo/SharpMap.Rendering.Cairo.Tests/Properties/AssemblyInfo.cs
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,35 @@ | ||
| using System.Reflection; | ||
| using System.Runtime.CompilerServices; | ||
| using System.Runtime.InteropServices; | ||
|
|
||
| // General Information about an assembly is controlled through the following | ||
| // set of attributes. Change these attribute values to modify the information | ||
| // associated with an assembly. | ||
| [assembly: AssemblyTitle("SharpMap.Rendering.Cairo.Tests")] | ||
| [assembly: AssemblyDescription("")] | ||
| [assembly: AssemblyConfiguration("")] | ||
| [assembly: AssemblyCompany("Microsoft")] | ||
| [assembly: AssemblyProduct("SharpMap.Rendering.Cairo.Tests")] | ||
| [assembly: AssemblyCopyright("Copyright © Microsoft 2009")] | ||
| [assembly: AssemblyTrademark("")] | ||
| [assembly: AssemblyCulture("")] | ||
|
|
||
| // Setting ComVisible to false makes the types in this assembly not visible | ||
| // to COM componenets. If you need to access a type in this assembly from | ||
| // COM, set the ComVisible attribute to true on that type. | ||
| [assembly: ComVisible(false)] | ||
|
|
||
| // The following GUID is for the ID of the typelib if this project is exposed to COM | ||
| [assembly: Guid("3d1c4bca-36fc-4538-8095-95b1035f6945")] | ||
|
|
||
| // Version information for an assembly consists of the following four values: | ||
| // | ||
| // Major Version | ||
| // Minor Version | ||
| // Build Number | ||
| // Revision | ||
| // | ||
| // You can specify all the values or you can default the Revision and Build Numbers | ||
| // by using the '*' as shown below: | ||
| [assembly: AssemblyVersion("1.0.0.0")] | ||
| [assembly: AssemblyFileVersion("1.0.0.0")] |
98 changes: 98 additions & 0 deletions
98
...pMap.Rendering/Cairo/SharpMap.Rendering.Cairo.Tests/SharpMap.Rendering.Cairo.Tests.csproj
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,98 @@ | ||
| <Project ToolsVersion="3.5" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> | ||
| <PropertyGroup> | ||
| <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration> | ||
| <Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform> | ||
| <ProductVersion>9.0.30729</ProductVersion> | ||
| <SchemaVersion>2.0</SchemaVersion> | ||
| <ProjectGuid>{58A46AA8-FCF0-4581-9CC0-937B124A5329}</ProjectGuid> | ||
| <OutputType>Library</OutputType> | ||
| <AppDesignerFolder>Properties</AppDesignerFolder> | ||
| <RootNamespace>SharpMap.Rendering.Cairo.Tests</RootNamespace> | ||
| <AssemblyName>SharpMap.Rendering.Cairo.Tests</AssemblyName> | ||
| <TargetFrameworkVersion>v2.0</TargetFrameworkVersion> | ||
| <FileAlignment>512</FileAlignment> | ||
| <ProjectTypeGuids>{3AC096D0-A1C2-E12C-1390-A8335801FDAB};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids> | ||
| </PropertyGroup> | ||
| <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' "> | ||
| <DebugSymbols>true</DebugSymbols> | ||
| <DebugType>full</DebugType> | ||
| <Optimize>false</Optimize> | ||
| <OutputPath>bin\Debug\</OutputPath> | ||
| <DefineConstants>DEBUG;TRACE</DefineConstants> | ||
| <ErrorReport>prompt</ErrorReport> | ||
| <WarningLevel>4</WarningLevel> | ||
| </PropertyGroup> | ||
| <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' "> | ||
| <DebugType>pdbonly</DebugType> | ||
| <Optimize>true</Optimize> | ||
| <OutputPath>bin\Release\</OutputPath> | ||
| <DefineConstants>TRACE</DefineConstants> | ||
| <ErrorReport>prompt</ErrorReport> | ||
| <WarningLevel>4</WarningLevel> | ||
| </PropertyGroup> | ||
| <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|x64' "> | ||
| <DebugSymbols>true</DebugSymbols> | ||
| <OutputPath>bin\x64\Debug\</OutputPath> | ||
| <DefineConstants>DEBUG;TRACE</DefineConstants> | ||
| <DebugType>full</DebugType> | ||
| <PlatformTarget>x64</PlatformTarget> | ||
| <CodeAnalysisUseTypeNameInSuppression>true</CodeAnalysisUseTypeNameInSuppression> | ||
| <CodeAnalysisModuleSuppressionsFile>GlobalSuppressions.cs</CodeAnalysisModuleSuppressionsFile> | ||
| <ErrorReport>prompt</ErrorReport> | ||
| </PropertyGroup> | ||
| <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|x64' "> | ||
| <OutputPath>bin\x64\Release\</OutputPath> | ||
| <DefineConstants>TRACE</DefineConstants> | ||
| <Optimize>true</Optimize> | ||
| <DebugType>pdbonly</DebugType> | ||
| <PlatformTarget>x64</PlatformTarget> | ||
| <CodeAnalysisUseTypeNameInSuppression>true</CodeAnalysisUseTypeNameInSuppression> | ||
| <CodeAnalysisModuleSuppressionsFile>GlobalSuppressions.cs</CodeAnalysisModuleSuppressionsFile> | ||
| <ErrorReport>prompt</ErrorReport> | ||
| </PropertyGroup> | ||
| <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|x86' "> | ||
| <DebugSymbols>true</DebugSymbols> | ||
| <OutputPath>bin\x86\Debug\</OutputPath> | ||
| <DefineConstants>DEBUG;TRACE</DefineConstants> | ||
| <DebugType>full</DebugType> | ||
| <PlatformTarget>x86</PlatformTarget> | ||
| <CodeAnalysisUseTypeNameInSuppression>true</CodeAnalysisUseTypeNameInSuppression> | ||
| <CodeAnalysisModuleSuppressionsFile>GlobalSuppressions.cs</CodeAnalysisModuleSuppressionsFile> | ||
| <ErrorReport>prompt</ErrorReport> | ||
| </PropertyGroup> | ||
| <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|x86' "> | ||
| <OutputPath>bin\x86\Release\</OutputPath> | ||
| <DefineConstants>TRACE</DefineConstants> | ||
| <Optimize>true</Optimize> | ||
| <DebugType>pdbonly</DebugType> | ||
| <PlatformTarget>x86</PlatformTarget> | ||
| <CodeAnalysisUseTypeNameInSuppression>true</CodeAnalysisUseTypeNameInSuppression> | ||
| <CodeAnalysisModuleSuppressionsFile>GlobalSuppressions.cs</CodeAnalysisModuleSuppressionsFile> | ||
| <ErrorReport>prompt</ErrorReport> | ||
| </PropertyGroup> | ||
| <ItemGroup> | ||
| <Reference Include="Microsoft.VisualStudio.QualityTools.UnitTestFramework, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL" /> | ||
| <Reference Include="System" /> | ||
| </ItemGroup> | ||
| <ItemGroup> | ||
| <Compile Include="Properties\AssemblyInfo.cs" /> | ||
| <Compile Include="UnitTest1.cs" /> | ||
| </ItemGroup> | ||
| <ItemGroup> | ||
| <Content Include="AuthoringTests.txt" /> | ||
| </ItemGroup> | ||
| <ItemGroup> | ||
| <ProjectReference Include="..\SharpMap.Rendering.Cairo\SharpMap.Rendering.Cairo.csproj"> | ||
| <Project>{132D6D22-8BC6-4D1C-A57C-04EF01C92456}</Project> | ||
| <Name>SharpMap.Rendering.Cairo</Name> | ||
| </ProjectReference> | ||
| </ItemGroup> | ||
| <Import Project="$(MSBuildBinPath)\Microsoft.CSharp.targets" /> | ||
| <!-- To modify your build process, add your task inside one of the targets below and uncomment it. | ||
| Other similar extension points exist, see Microsoft.Common.targets. | ||
| <Target Name="BeforeBuild"> | ||
| </Target> | ||
| <Target Name="AfterBuild"> | ||
| </Target> | ||
| --> | ||
| </Project> |
Oops, something went wrong.