11 | Hi! This is my second design for OSWD, with CSS and XHTML 1.0 Transitional Validation.
12 | You can do whatever you want with this template, just keep the Hosting Colombia
13 | link at the bottom. Enjoy!
14 |
15 |
16 | Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Curabitur id est tincidunt
17 | nisl pellentesque tincidunt. Donec in mauris. Mauris neque magna, consectetuer id,
18 | malesuada vitae, tincidunt sit amet, mi. Aliquam lacinia. Suspendisse potenti. Proin
19 | justo lorem, rutrum ac, facilisis in, malesuada sed, ligula. Mauris lobortis lacus
20 | at nibh. Aenean vitae odio vel odio placerat hendrerit. Suspendisse lacus lacus,
21 | tempor id, pharetra eget, ornare sit amet, pede. Sed aliquet, justo ac elementum
22 | pretium, arcu leo placerat est, a luctus purus diam eget arcu. Nam augue diam, mollis
23 | a, scelerisque eget, aliquet condimentum, pede. Vestibulum tristique lectus sed
24 | augue.
25 |
26 |
27 | Some Title Here
28 |
29 | Nullam et ipsum condimentum pede luctus consequat. Nulla venenatis mi a sapien.
30 | Nunc facilisis pede quis nisl. Duis eget sapien. Suspendisse potenti. Vestibulum
31 | eget ligula in ante pharetra imperdiet. Maecenas vehicula luctus mi. Suspendisse
32 | molestie libero vitae magna. Integer metus tortor, mollis eleifend, tincidunt in,
33 | sagittis eget, lorem. Donec posuere. Curabitur ut eros. Praesent vitae sem facilisis
34 | tellus euismod scelerisque. Donec pellentesque. Vestibulum scelerisque, turpis pellentesque
35 | sollicitudin nonummy, ipsum erat consequat augue, ut tincidunt urna magna ut leo.
36 | Nullam ullamcorper metus vitae est. Ut diam metus, molestie porttitor, pretium vitae,
37 | ultricies nec, pede. Maecenas bibendum dictum tellus. Vestibulum feugiat, velit
38 | quis eleifend pharetra, leo lacus laoreet diam, quis laoreet arcu mi vel felis.
39 |
40 |
41 |
42 |
43 |
--------------------------------------------------------------------------------
/ThirdParty/NUnit/samples/csharp/failures/AssemblyInfo.cs:
--------------------------------------------------------------------------------
1 | using System.Reflection;
2 | using System.Runtime.CompilerServices;
3 |
4 | //
5 | // General Information about an assembly is controlled through the following
6 | // set of attributes. Change these attribute values to modify the information
7 | // associated with an assembly.
8 | //
9 | [assembly: AssemblyTitle("csharp.sample.dll")]
10 | [assembly: AssemblyDescription("C# Sample Unit Tests")]
11 | [assembly: AssemblyConfiguration("")]
12 | [assembly: AssemblyCompany("NUnit")]
13 | [assembly: AssemblyProduct("NUnit")]
14 | [assembly: AssemblyCopyright("Copyright (C) 2002-2003 James W. Newkirk, Michael C. Two, Alexei A. Vorontsov. \nCopyright (C) 2000-2003 Philip Craig.\nAll Rights Reserved.")]
15 | [assembly: AssemblyTrademark("")]
16 | [assembly: AssemblyCulture("")]
17 |
18 | //
19 | // Version information for an assembly consists of the following four values:
20 | //
21 | // Major Version
22 | // Minor Version
23 | // Build Number
24 | // Revision
25 | //
26 | // You can specify all the values or you can default the Revision and Build Numbers
27 | // by using the '*' as shown below:
28 |
29 | [assembly: AssemblyVersion("2.2.0.0")]
30 |
31 | //
32 | // In order to sign your assembly you must specify a key to use. Refer to the
33 | // Microsoft .NET Framework documentation for more information on assembly signing.
34 | //
35 | // Use the attributes below to control which key is used for signing.
36 | //
37 | // Notes:
38 | // (*) If no key is specified, the assembly is not signed.
39 | // (*) KeyName refers to a key that has been installed in the Crypto Service
40 | // Provider (CSP) on your machine. KeyFile refers to a file which contains
41 | // a key.
42 | // (*) If the KeyFile and the KeyName values are both specified, the
43 | // following processing occurs:
44 | // (1) If the KeyName can be found in the CSP, that key is used.
45 | // (2) If the KeyName does not exist and the KeyFile does exist, the key
46 | // in the KeyFile is installed into the CSP and used.
47 | // (*) In order to create a KeyFile, you can use the sn.exe (Strong Name) utility.
48 | // When specifying the KeyFile, the location of the KeyFile should be
49 | // relative to the project output directory which is
50 | // %Project Directory%\obj\. For example, if your KeyFile is
51 | // located in the project directory, you would specify the AssemblyKeyFile
52 | // attribute as [assembly: AssemblyKeyFile("..\\..\\mykey.snk")]
53 | // (*) Delay Signing is an advanced option - see the Microsoft .NET Framework
54 | // documentation for more information on this.
55 | //
56 | [assembly: AssemblyDelaySign(false)]
57 | [assembly: AssemblyKeyFile("")]
58 | [assembly: AssemblyKeyName("")]
59 |
--------------------------------------------------------------------------------
/SUFORS V.1/Src/Web/MasterPage.master:
--------------------------------------------------------------------------------
1 | <%@ Register TagPrefix="uc" TagName="MainMenu" Src="~/UserControls/MainMenu.ascx" %>
2 | <%@ Register TagPrefix="uc" TagName="UserInfoBar" Src="~/UserControls/UserInfoBar.ascx" %>
3 | <%@ Master Language="C#" AutoEventWireup="true" CodeFile="MasterPage.master.cs" Inherits="MasterPage" %>
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
59 |
60 |
61 |
--------------------------------------------------------------------------------
/SUFORS V.1/Src/Web/ReportEdit.aspx:
--------------------------------------------------------------------------------
1 | <%@ Page Title="" Language="C#" MasterPageFile="~/MasterPage.master" AutoEventWireup="true" CodeFile="ReportEdit.aspx.cs" Inherits="ReportEdit" %>
2 |
3 |
4 |
5 |
6 | Home
7 |
9 |
11 |
13 |
14 |
15 |
17 |
18 | Id:
19 |
20 |
21 | Location:
22 |
24 |
25 | Description:
26 |
28 |
29 |
30 |
31 | Location:
32 |
34 |
35 | Description:
36 |
38 |
39 |
40 |
41 |
46 |
47 |
48 |
49 |
50 |
51 |
52 |
53 |
54 |
55 |
56 |
57 |
58 |
59 |
60 |
61 |
--------------------------------------------------------------------------------
/ThirdParty/NUnit/doc/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | NUnit - DocHome
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
This documentation covers the NUnit 2.5 release,
30 | introducing a large set of new features to NUnit, particularly in
31 | the area of parameterized or data-driven testing.
32 |
33 |
Where applicable, we have marked sections with the version in which a feature
34 | first appeared.
35 |
36 |
If you are new to NUnit, we suggest you begin by reading the
37 | Getting Started section of this site.
38 | Those who have used earlier releases may want to begin with the
39 | Upgrading section.
40 |
41 |
See the
42 | Release Notes for more information on this release.
43 |
44 |
All documentation is included in the release packages of NUnit. Beginning with NUnit
45 | 2.4.2, you may choose to download the documentation
46 | separately.
NUnit is designed to be extended in a number of ways.
30 |
31 |
Extensions to the NUnit framework - the part of NUnit that is referenced
32 | by tests - usually take the form of
33 | Custom Constaints, written by users to
34 | encapsulate tests that pertain to their specific projects.
35 |
36 |
Extending the features found within NUnit itself depends on the use of
37 | NUnit Addins.
38 | Currently, The Addin mechanism only supports extensions to the NUnit core -
39 | the part of NUnit that builds and executes test suites. However, the API that
40 | is used provides for the future ability to extend the client side of NUnit,
41 | including the GUI.
If you haven't already done so, go to our Download page, select a version of NUnit and download it. The
30 | Installation page
31 | contains instructions for installing on your system.
32 |
33 |
To get started using NUnit, read the Quick Start page. This article demonstrates the development process with NUnit in the
34 | context of a C# banking application. Check the
35 | Samples page for additional examples,
36 | including some in VB.Net, J# and managed C++.
37 |
38 |
Which Test Runner to use?
39 |
40 |
NUnit has two different ways to run your tests. The
41 | console runner, nunit-console.exe,
42 | is the fastest to launch, but is not interactive.
43 | The gui runner,
44 | nunit-gui.exe, is a Windows Forms application that allows you to work
45 | selectively with your tests and provides graphical feedback.
The nunit-console.exe program is a text-based runner and can be used when you
29 | want to run all your tests and don’t need a red/yellow/green indication of
30 | success or failure.
31 |
It is useful for automation of tests and integration into other systems. It
32 | automatically saves its results in XML format, allowing you to produce reports
33 | or otherwise process the results. The following is a screenshot of the console
34 | program.
35 |
36 |
37 |
38 |
39 |
In this example, nunit-console has just run the tests in the mock-assembly.dll
40 | that is part of the NUnit distribution. This assembly contains a number of tests, some
41 | of which are either ignored or marked explicit. The summary line shows the
42 | result of the test run. Click here
43 | to see the XML produced for this test run.
44 |
45 |
The .NET 2.0 version of the nunit-console program is built using /platform:anycpu,
46 | which causes it to be jit-compiled to 32-bit code on a 32-bit system and 64-bit code
47 | on a 64 bit system. This causes an exception when NUnit is used to test a 32-bit
48 | application on a 64-bit system. To avoid this problem, use the nunit-console-x86
49 | program, which is built using /platform:x86, when testing 32-bit code on a
50 | 64-bit system.
51 |
52 |
PNUnit stands for "Parallel NUnit." It is an extension of NUNit
30 | developed by Pablo Santos Luaces and his team at Codice Software for
31 | their internal use in testing the Plastic (TM) Software Configuration
32 | Management System. Codice released PNUnit to the community in 2007.
33 |
34 |
As part of the NUnit 2.5 release, we worked with the NUnit and PNUnit
35 | teams worked together to make PNUnit work with NUnit without any modifications.
36 | PNUnit is now included in the NUnit distribution.
37 |
38 |
How it Works
39 |
40 |
PNUnit is not intended for "casual" parallelism merely to
41 | make the tests run faster. Rather, it's intended as a way to test
42 | applications composed of distributed, communicating components. Tests
43 | of each component run in parallel and use memory barriers to synchronize
44 | their operation.
45 |
46 |
PNUnit uses a special executable to launch its tests.
47 | The launcher reads an xml file that specifies the tests to be
48 | executed and where they should run, whether on the same machine or
49 | on another machine on the network.
50 |
51 |
A SameAsConstraint is used to test whether the object passed
30 | as an actual value has the same identity as the object supplied
31 | in its constructor.
32 |
33 |
A SuiteBuilder is an addin used to build a test fixture from a type. NUnit itself
31 | uses a SuiteBuilder to recognize and build TestFixtures.
32 |
33 |
Extension Point
34 |
An addin may use the host to access this extension point by name:
35 |
36 |
The extension object passed to Install must implement the ISuiteBuilder interface:
41 |
42 |
43 | public interface ISuiteBuilder
44 | {
45 | bool CanBuildFrom( Type type );
46 | Test BuildFrom( Type type );
47 | }
48 |
49 |
50 |
CanBuildFrom should return true if the specified Type is one from which
51 | the builder is able to create a fixture. This usually involve examining
52 | the Type and its attriutes.
53 |
54 |
The BuildFrom method should return a test fixture completely populated
55 | with its contained test cases. Return null if it is not possible to
56 | build a fixture using the provided Type.
57 |
58 |
59 |
The HasDataFor method should return true if the provider is able to
51 | supply data for the specified parameter. If a provider only wants to be used
52 | on certain types of tests, it can examine the supplied ParameterInfo and
53 | its associated MethodInfo and Type.
54 |
55 |
The GetDataFor method should return a list of individual values to
56 | use for the supplied parameter in running the test.
57 |
58 |
This software is provided 'as-is', without any express or implied warranty. In
34 | no event will the authors be held liable for any damages arising from the use
35 | of this software.
36 |
Permission is granted to anyone to use this software for any purpose, including
37 | commercial applications, and to alter it and redistribute it freely, subject to
38 | the following restrictions:
39 |
1. The origin of this software must not be misrepresented; you must not claim
40 | that you wrote the original software. If you use this software in a product, an
41 | acknowledgment (see the following) in the product documentation is required.
2. Altered source versions must be plainly marked as such, and must not be
46 | misrepresented as being the original software.
47 |
3. This notice may not be removed or altered from any source distribution.
48 |
49 |
License Note
50 |
This license is based on
51 | the open source zlib/libpng license. The idea was to keep the license
52 | as simple as possible to encourage use of NUnit in free and commercial
53 | applications and libraries, but to keep the source code together and to give
54 | credit to the NUnit contributors for their efforts. While this license allows
55 | shipping NUnit in source and binary form, if shipping a NUnit variant is the
56 | sole purpose of your product, please let
57 | us know.
Beginning with version 2.2.1, old style test cases ("Test....") are no longer
30 | recognized by default. We recommend that you convert such test cases to use the
31 | TestAttribute. Alternatively, you may
32 | specify a setting in the test config file to allow use of old style test cases by
33 | default.
34 |
35 |
Beginning with NUnit 2.2.2, NUnit is able to run tests Built with older
36 | versions of NUnit 2.x without recompilation. Note that you must have an
37 | available copy of the nunit.framework assembly from the older version
38 | in order for your tests to load correctly.
39 |
40 |
From NUnit 1.x
41 |
42 |
NUnit 2.5 no longer supports inheriting from TestCase when defining a test.
43 | If you need to run such tests, you may continue to do so using the
44 | a 2.4.x or earlier version of the nunit.framework assembly. Of course, you
45 | will not be able to use new features introduced in 2.5 if you follow this
46 | course.
47 |
48 |
For a complete conversion to 2.5, you should modify and recompile your tests
49 | using the new version of NUnit.
50 |
51 |
Suite property
52 |
The NUnit 1.x Suite property will not be found by the new program. These must be
53 | changed to the "Suite" attribute for the test runners to find them.
54 | Another alternative is that these suites are no longer needed due to the
55 | automatic capability that is built in to the new version.
56 |
57 |
AssertionFailedError
58 |
If you have written code expecting the exception AssertionFailedError, this must
59 | be changed to AssertionException.
