Skip to content

Commit 19d6bf2

Browse files
mitchelsellersmitchelsellers
committed
Migration from CodePlex & Modernization of build process. No project shcnages made as part of this commit
1 parent 2c74f5d commit 19d6bf2

40 files changed

+5678
-0
lines changed

‎Documentation/Documents_04.01.02_ReleaseNotes.txt

+16
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
2+
Version 4.1.2 of the core Documents module.
3+
This version requires Visual Studio 2010 for development (compiling against 2.0 framework) and also DotNetNuke core 4.6.2 or greater.
4+
5+
This release corrects the following changes:
6+
7+
Corrected a problems related to the URL control and non-existant files (primary reason for release).
8+
Fixed bugs found in release candidate 4.1.1 release packaging (which then created errors exposed in the user interface).
9+
Deleted legacy files.
10+
Upgraded module to Visual Studio 2010 for development.
11+
Added Documentation folder.
12+
Finished proper conversion to WAP for vs 2010.
13+
Removed usage of legacy connection string.
14+
Updated copyright.
15+
Putting source under CodePlex source control as of this release.
16+
Updated build file to work with 64 bit file system (and newer versions of nAnt).

‎Documentation/Documents_04.01.02_TestCases.txt

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---------------------------------------------------------------------------------------
2+
3+
DNN Documents Module
4+
5+
Test Cases: Version 03.01.06
6+
7+
----------------------------------------------------------------------------------------
8+
9+
none

‎Documentation/Documents_05.00.00_ReleaseNotes.txt

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
See manifest file for full documentation

‎Documentation/Documents_05.00.00_TestCases.txt

+14
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---------------------------------------------------------------------------------------
2+
3+
DNN Documents Module
4+
5+
Test Cases: Version 05.00.00
6+
7+
----------------------------------------------------------------------------------------
8+
9+
Upgrade Validation Test
10+
11+
* Start with install of 04.01.02
12+
* Observe documented errors on document update and settings
13+
* Install 05.00.00
14+
* Module should now function properly

‎Source/DnnDocuments/04.01.02.txt

+10
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
install\module\Documents_03.01.06_Install.resources
2+
install\module\Documents_04.01.00_Install.resources
3+
bin\DotNetNuke.Modules.Documents.SqlDataProvider.dll
4+
DesktopModules\Documents\Providers\DataProviders\SQLDataProvider\DotNetNuke.Documents.SqlDataProvider.vbproj
5+
DesktopModules\Documents\Providers\DataProviders\SQLDataProvider\AssemblyInfo.vb
6+
DesktopModules\Documents\Documents_03.01.02_ReleaseNotes.txt
7+
DesktopModules\Documents\Documents_03.01.03_ReleaseNotes.txt
8+
DesktopModules\Documents\Documents_03.01.04_ReleaseNotes.txt
9+
DesktopModules\Documents\Documents_03.01.05_ReleaseNotes.txt
10+
DesktopModules\Documents\Documents_04.00.00_ReleaseNotes.txt

‎Source/DnnDocuments/App_LocalResources/Document.ascx.resx

+239
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,239 @@
1+
<?xml version="1.0" encoding="utf-8"?>
2+
<root>
3+
<!--
4+
Microsoft ResX Schema
5+
6+
Version 2.0
7+
8+
The primary goals of this format is to allow a simple XML format
9+
that is mostly human readable. The generation and parsing of the
10+
various data types are done through the TypeConverter classes
11+
associated with the data types.
12+
13+
Example:
14+
15+
... ado.net/XML headers & schema ...
16+
<resheader name="resmimetype">text/microsoft-resx</resheader>
17+
<resheader name="version">2.0</resheader>
18+
<resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
19+
<resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
20+
<data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
21+
<data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
22+
<data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
23+
<value>[base64 mime encoded serialized .NET Framework object]</value>
24+
</data>
25+
<data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
26+
<value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
27+
<comment>This is a comment</comment>
28+
</data>
29+
30+
There are any number of "resheader" rows that contain simple
31+
name/value pairs.
32+
33+
Each data row contains a name, and value. The row also contains a
34+
type or mimetype. Type corresponds to a .NET class that support
35+
text/value conversion through the TypeConverter architecture.
36+
Classes that don't support this are serialized and stored with the
37+
mimetype set.
38+
39+
The mimetype is used for serialized objects, and tells the
40+
ResXResourceReader how to depersist the object. This is currently not
41+
extensible. For a given mimetype the value must be set accordingly:
42+
43+
Note - application/x-microsoft.net.object.binary.base64 is the format
44+
that the ResXResourceWriter will generate, however the reader can
45+
read any of the formats listed below.
46+
47+
mimetype: application/x-microsoft.net.object.binary.base64
48+
value : The object must be serialized with
49+
: System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
50+
: and then encoded with base64 encoding.
51+
52+
mimetype: application/x-microsoft.net.object.soap.base64
53+
value : The object must be serialized with
54+
: System.Runtime.Serialization.Formatters.Soap.SoapFormatter
55+
: and then encoded with base64 encoding.
56+
57+
mimetype: application/x-microsoft.net.object.bytearray.base64
58+
value : The object must be serialized into a byte array
59+
: using a System.ComponentModel.TypeConverter
60+
: and then encoded with base64 encoding.
61+
-->
62+
<xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
63+
<xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
64+
<xsd:element name="root" msdata:IsDataSet="true">
65+
<xsd:complexType>
66+
<xsd:choice maxOccurs="unbounded">
67+
<xsd:element name="metadata">
68+
<xsd:complexType>
69+
<xsd:sequence>
70+
<xsd:element name="value" type="xsd:string" minOccurs="0" />
71+
</xsd:sequence>
72+
<xsd:attribute name="name" use="required" type="xsd:string" />
73+
<xsd:attribute name="type" type="xsd:string" />
74+
<xsd:attribute name="mimetype" type="xsd:string" />
75+
<xsd:attribute ref="xml:space" />
76+
</xsd:complexType>
77+
</xsd:element>
78+
<xsd:element name="assembly">
79+
<xsd:complexType>
80+
<xsd:attribute name="alias" type="xsd:string" />
81+
<xsd:attribute name="name" type="xsd:string" />
82+
</xsd:complexType>
83+
</xsd:element>
84+
<xsd:element name="data">
85+
<xsd:complexType>
86+
<xsd:sequence>
87+
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
88+
<xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
89+
</xsd:sequence>
90+
<xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
91+
<xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
92+
<xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
93+
<xsd:attribute ref="xml:space" />
94+
</xsd:complexType>
95+
</xsd:element>
96+
<xsd:element name="resheader">
97+
<xsd:complexType>
98+
<xsd:sequence>
99+
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
100+
</xsd:sequence>
101+
<xsd:attribute name="name" type="xsd:string" use="required" />
102+
</xsd:complexType>
103+
</xsd:element>
104+
</xsd:choice>
105+
</xsd:complexType>
106+
</xsd:element>
107+
</xsd:schema>
108+
<resheader name="resmimetype">
109+
<value>text/microsoft-resx</value>
110+
</resheader>
111+
<resheader name="version">
112+
<value>2.0</value>
113+
</resheader>
114+
<resheader name="reader">
115+
<value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
116+
</resheader>
117+
<resheader name="writer">
118+
<value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
119+
</resheader>
120+
<data name="AddContent.Action" xml:space="preserve">
121+
<value>Add New Document</value>
122+
</data>
123+
<data name="Title.Text" xml:space="preserve">
124+
<value>Title</value>
125+
</data>
126+
<data name="CreatedBy.Text" xml:space="preserve">
127+
<value>Created By</value>
128+
</data>
129+
<data name="DownloadLink.Text" xml:space="preserve">
130+
<value>Download</value>
131+
</data>
132+
<data name="CreatedDate.Text" xml:space="preserve">
133+
<value>Created Date</value>
134+
</data>
135+
<data name="Description.Text" xml:space="preserve">
136+
<value>Description</value>
137+
</data>
138+
<data name="SortIndex.Text" xml:space="preserve">
139+
<value>Sort Index</value>
140+
</data>
141+
<data name="ModifiedBy.Text" xml:space="preserve">
142+
<value>Modified By</value>
143+
</data>
144+
<data name="ModifiedDate.Text" xml:space="preserve">
145+
<value>Modified Date</value>
146+
</data>
147+
<data name="Owner.Text" xml:space="preserve">
148+
<value>Owner</value>
149+
</data>
150+
<data name="Category.Text" xml:space="preserve">
151+
<value>Category</value>
152+
</data>
153+
<data name="LastUpdated.Text" xml:space="preserve">
154+
<value>Last Updated</value>
155+
</data>
156+
<data name="Size.Text" xml:space="preserve">
157+
<value>Size</value>
158+
</data>
159+
<data name="ModuleHelp.Text" xml:space="preserve">
160+
<value>&lt;h1&gt;About the Documents Module&lt;/h1&gt;
161+
&lt;p&gt;The Documents Module produces a list of documents with links to view or
162+
download the document (depending on the user's browser settings). Documents can
163+
be located within the portal, or can be a link to another website or portal.
164+
&lt;/p&gt;
165+
&lt;p&gt;
166+
The document title, category, description, document owner, name of the user who
167+
created the document, the user who last updated the document, creation date,
168+
the date that the document was added or last updated, and the file size
169+
(internal documents only) are available for each listing. Link click tracking
170+
and logging are also available.
171+
&lt;/p&gt;
172+
&lt;p&gt;
173+
In the module settings page, you can configure the columns that are displayed,
174+
the column order&amp;nbsp;and the sort order of the documents listed. The documents
175+
module supports the DotNetNuke core "secure storage" feature, so that documents
176+
stored securely are not available to unauthorized users.
177+
&lt;/p&gt;
178+
&lt;h1&gt;Document Module Settings&lt;/h1&gt;
179+
&lt;ol&gt;
180+
&lt;li&gt;
181+
&lt;b&gt;Use Documents Categories List:&lt;/b&gt;
182+
Sets whether to use a free-text field for the document category field, or use a
183+
list defined in the Host-&amp;gt;Lists page. If you want to use a drop-down list,
184+
create a list in the Lists page called "Document Categories".
185+
&lt;li&gt;
186+
&lt;b&gt;Show Title Link:&lt;/b&gt;
187+
Sets whether or not to show the document title (if included in the display
188+
columns) as a hyperlink to the document.
189+
&lt;li&gt;
190+
&lt;b&gt;Display Columns: &lt;/b&gt;
191+
Sets which columns to display, and allows you to set what order to display the
192+
columns in.
193+
&lt;li&gt;
194+
&lt;b&gt;Sorting: &lt;/b&gt;Sets the sort order that documents are displayed in. You can
195+
add multiple sort orders to add more than one "key" to sort by.
196+
&lt;/li&gt;
197+
&lt;/ol&gt;
198+
&lt;h1&gt;Add a Document&lt;/h1&gt;
199+
&lt;ol&gt;
200+
&lt;li&gt;
201+
Add a &lt;b&gt;Documents&lt;/b&gt; module, or go to an existing &lt;b&gt;Documents&lt;/b&gt;
202+
module.
203+
&lt;li&gt;
204+
Click &lt;b&gt;Add New Document&lt;/b&gt;.
205+
&lt;li&gt;
206+
At &lt;b&gt;Title&lt;/b&gt;, enter a title for the document.
207+
&lt;li&gt;
208+
At &lt;b&gt;Link Type&lt;/b&gt;, select &lt;b&gt;URL&lt;/b&gt; or &lt;b&gt;File&lt;/b&gt; and then at &lt;b&gt;Link&lt;/b&gt;
209+
select or enter the required URL or file.
210+
&lt;li&gt;
211+
At &lt;b&gt;Track Number Of Times This Link Is Clicked?&lt;/b&gt;
212+
(optional), check the box if required.
213+
&lt;li&gt;
214+
At &lt;b&gt;Log The User, Date, And Time For Every Link Click&lt;/b&gt;
215+
(optional), check the box if required.
216+
&lt;li&gt;
217+
At &lt;b&gt;Category&lt;/b&gt;
218+
(optional), enter a category for the document.
219+
&lt;li&gt;
220+
Click &lt;b&gt;Update&lt;/b&gt;.&lt;/li&gt;
221+
&lt;/ol&gt;
222+
&lt;h1&gt;CSS Styling for the Documents Module&lt;/h1&gt;
223+
&lt;P&gt;The documents module renders an "outside" DIV tag with a CLASS attribute of
224+
"DNN_Documents". Each header cell has a CLASS attribute of [Name]Header, where
225+
[Name] is the column name - for example "TitleHeader", "SizeHeader",
226+
"CategoryHeader". Each data cell has a CLASS attribute of [Name]Item, for
227+
example "TitleItem", "SizeItem", "CategoryItem".&lt;/P&gt;
228+
&lt;P&gt;This allows skin developers to control the CSS style of individual columns.
229+
For example, use the following CSS to render the size column in red and set the
230+
column width to 50 pixels:&lt;/P&gt;
231+
&lt;P&gt;&lt;FONT face="Courier New" size="2"&gt;&amp;nbsp; .DNN_Documents .SizeItem {color: red;
232+
width: 50px} &lt;/FONT&gt;
233+
&lt;/P&gt;
234+
</value>
235+
</data>
236+
<data name="Clicks.Text" xml:space="preserve">
237+
<value>Clicks</value>
238+
</data>
239+
</root>

0 commit comments

Comments
 (0)