This commit is contained in:
2026-04-17 14:55:32 -04:00
commit bc3ac1d4c9
18017 changed files with 4371742 additions and 0 deletions

View File

@@ -0,0 +1 @@
12

View File

@@ -0,0 +1 @@
12

View File

@@ -0,0 +1,40 @@
<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="3.5">
<PropertyGroup>
<!-- Select a Product Configuration -->
<InstallShieldProductConfiguration>Express</InstallShieldProductConfiguration>
<!-- Select a Visual Studio Configuration / InstallShield Release -->
<Configuration>Debug</Configuration>
<InstallShieldRelease>$(Configuration)</InstallShieldRelease>
</PropertyGroup>
<ItemGroup>
<!-- The InstallShieldProject item selects the project to build -->
<InstallShieldProject Include="$(MSBuildProjectDirectory)\$(MSBuildProjectName).isl"/>
<!-- The InstallShieldReleaseFlags sets Release Flags -->
<!--<InstallShieldReleaseFlags Include=""/>-->
<!-- The InstallShieldMergeModulePath specifies what directories are
searched for Merge Modules -->
<!--<InstallShieldMergeModulePath Include=""/>-->
</ItemGroup>
<ItemGroup>
<!-- The ProjectReference items refer to any Visual Studio solutions you want to automatically probe for Project Output Groups. -->
</ItemGroup>
<ItemGroup>
<!-- The TaggedOutputs items allow you to explicitly add extra files to output groups. Each item must include both Name and OutputGroup, as well as TargetPath metadata values. -->
<!--<TaggedOutputs Include="C:\My Test Exe.exe">
<Name>My Test Project</Name>
<OutputGroup>Primary output</OutputGroup>
<TargetPath>My Test Exe.exe</TargetPath>
</TaggedOutputs> -->
</ItemGroup>
<Import Project="$(MSBuildExtensionsPath32)\InstallShield\2012SpringLimited\InstallShield.targets"/>
<ItemGroup>
<ProjectReference Include="..\DataPRO\DataPRO.csproj">
<Name>DataPRO</Name>
<Project>{8BAA9433-8034-4FDE-822C-537C59D3A7EC}</Project>
</ProjectReference>
<ProjectReference Include="..\Storage\Storage.csproj">
<Name>Storage</Name>
<Project>{FE155189-658B-4CA5-B387-2B6D79BCCBD0}</Project>
</ProjectReference>
</ItemGroup>
</Project>

Binary file not shown.

After

Width:  |  Height:  |  Size: 314 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 300 KiB

View File

@@ -0,0 +1,15 @@
• DataPRO 1.9 can be installed as a 32- or 64-bit system.
o Select the correct option based on your PC operating system.
• The database structure for a local installation of DataPRO has changed for DataPRO 1.9.
o DataPRO 1.9 utilizes SQL Server for both local and centralized installations.
o SQLLocalDb 2014 is included with the DataPRO software package and installed if needed for a local database.
o DataPRO 1.9 is compatible with newer versions of SQLLocalDb 2014, and SQLLocalDb 2014 will not be installed if a newer version is found.
o Database files run with newer versions of SQLLocalDb are not backwards compatible with older versions.
o Database files opened in newer versions of SQL Server Management Studio will be updated and will become incompatible with older versions.
• If installing as a centralized Database, the database must be manually attached to the server.
o DataPRO 1.9 operates on two database files, DataPRO.mdf and ISO.mdf; both of which must be attached to the server.
o This often requires support from facilities/IT.
• Do not change the name of the Database during installation.
o Database name should remain DataPRO.
• Database files for a local installation of DataPRO 1.9 can be copied to another instance of DataPRO 1.9.
o Both DataPRO.mdf and DataPRO_log.mdf must be copied.

Binary file not shown.

After

Width:  |  Height:  |  Size: 310 KiB

Binary file not shown.

Binary file not shown.

File diff suppressed because it is too large Load Diff

View File

@@ -0,0 +1,40 @@
<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="3.5">
<PropertyGroup>
<!-- Select a Product Configuration -->
<InstallShieldProductConfiguration>Express</InstallShieldProductConfiguration>
<!-- Select a Visual Studio Configuration / InstallShield Release -->
<Configuration>Debug</Configuration>
<InstallShieldRelease>$(Configuration)</InstallShieldRelease>
</PropertyGroup>
<ItemGroup>
<!-- The InstallShieldProject item selects the project to build -->
<InstallShieldProject Include="$(MSBuildProjectDirectory)\$(MSBuildProjectName).isl"/>
<!-- The InstallShieldReleaseFlags sets Release Flags -->
<!--<InstallShieldReleaseFlags Include=""/>-->
<!-- The InstallShieldMergeModulePath specifies what directories are
searched for Merge Modules -->
<!--<InstallShieldMergeModulePath Include=""/>-->
</ItemGroup>
<ItemGroup>
<!-- The ProjectReference items refer to any Visual Studio solutions you want to automatically probe for Project Output Groups. -->
</ItemGroup>
<ItemGroup>
<!-- The TaggedOutputs items allow you to explicitly add extra files to output groups. Each item must include both Name and OutputGroup, as well as TargetPath metadata values. -->
<!--<TaggedOutputs Include="C:\My Test Exe.exe">
<Name>My Test Project</Name>
<OutputGroup>Primary output</OutputGroup>
<TargetPath>My Test Exe.exe</TargetPath>
</TaggedOutputs> -->
</ItemGroup>
<Import Project="$(MSBuildExtensionsPath32)\InstallShield\2012SpringLimited\InstallShield.targets"/>
<ItemGroup>
<ProjectReference Include="..\DataPRO\DataPRO.csproj">
<Name>DataPRO</Name>
<Project>{8BAA9433-8034-4FDE-822C-537C59D3A7EC}</Project>
</ProjectReference>
<ProjectReference Include="..\Storage\Storage.csproj">
<Name>Storage</Name>
<Project>{FE155189-658B-4CA5-B387-2B6D79BCCBD0}</Project>
</ProjectReference>
</ItemGroup>
</Project>

File diff suppressed because it is too large Load Diff

Binary file not shown.

Binary file not shown.

After

Width:  |  Height:  |  Size: 310 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 314 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 300 KiB

View File

@@ -0,0 +1,15 @@
• DataPRO 1.9 can be installed as a 32- or 64-bit system.
o Select the correct option based on your PC operating system.
• The database structure for a local installation of DataPRO has changed for DataPRO 1.9.
o DataPRO 1.9 utilizes SQL Server for both local and centralized installations.
o SQLLocalDb 2014 is included with the DataPRO software package and installed if needed for a local database.
o DataPRO 1.9 is compatible with newer versions of SQLLocalDb 2014, and SQLLocalDb 2014 will not be installed if a newer version is found.
o Database files run with newer versions of SQLLocalDb are not backwards compatible with older versions.
o Database files opened in newer versions of SQL Server Management Studio will be updated and will become incompatible with older versions.
• If installing as a centralized Database, the database must be manually attached to the server.
o DataPRO 1.9 operates on two database files, DataPRO.mdf and ISO.mdf; both of which must be attached to the server.
o This often requires support from facilities/IT.
• Do not change the name of the Database during installation.
o Database name should remain DataPRO.
• Database files for a local installation of DataPRO 1.9 can be copied to another instance of DataPRO 1.9.
o Both DataPRO.mdf and DataPRO_log.mdf must be copied.

Binary file not shown.

File diff suppressed because it is too large Load Diff

View File

@@ -0,0 +1 @@
12

View File

@@ -0,0 +1 @@
12

Some files were not shown because too many files have changed in this diff Show More