Search found 1290 matches
- Mon Sep 26, 2016 12:58 pm
- Forum: Integration Development
- Topic: select 4.0 package on select 4.1
- Replies: 12
- Views: 1855
Re: select 4.0 package on select 4.1
You cannot build a Select 4.1 package in VS2010 since we use .NET 4.6. You must use VS2015.
- Fri Sep 23, 2016 2:59 pm
- Forum: Integration Development
- Topic: Formulas - Training Material
- Replies: 1
- Views: 529
Re: Formulas - Training Material
The Select SDK is the primary product for creating Select Shell and Server API packages - as well as C# standalone applications. It provides several project templates for VS2015 and a help file with code examples, explanatory help topics, and interface and object API definitions. Talk to your SoftPr...
- Fri Sep 23, 2016 12:32 pm
- Forum: Integration Development
- Topic: select 4.0 package on select 4.1
- Replies: 12
- Views: 1855
Re: select 4.0 package on select 4.1
Is it possible that you are using the "spregpkg.exe" from the Select 4.0 SDK instead of the Select 4.1?
- Fri Sep 23, 2016 11:58 am
- Forum: Integration Development
- Topic: select 4.0 package on select 4.1
- Replies: 12
- Views: 1855
Re: select 4.0 package on select 4.1
It looks like your project is still referencing the Select 4.0 DLLs during your package build. Are there other projects in your package that might be referencing the old DLLs? I have found that even though the VS Project does not specify a specific DLL version, it has trouble updating the informatio...
- Thu Sep 22, 2016 10:02 am
- Forum: Custom Order Rules
- Topic: Stop Adding Custom Order Reports
- Replies: 3
- Views: 1138
Re: Stop Adding Custom Order Reports
The default CORs can be removed in a similar way to how they were originally added - by selecting an order with no COR modules as the default order. Create a new order. Open SoftPro Development Studio (Shift + F12) Delete all order modules. Right click on the order in the Project Explorer and select...
- Wed Sep 21, 2016 1:52 pm
- Forum: Integration Development
- Topic: select 4.0 package on select 4.1
- Replies: 12
- Views: 1855
Re: select 4.0 package on select 4.1
The Runtime version is the .NET version that VS thinks should be adequate to run the DLL. The Version property is the version of the DLL. You should ignore the displayed runtime version. If Version is 4.1.0.0, you should be pointing to the correct DLLs.
- Wed Sep 21, 2016 10:19 am
- Forum: Integration Development
- Topic: select 4.0 package on select 4.1
- Replies: 12
- Views: 1855
Re: select 4.0 package on select 4.1
The issue is that the Select DLLs have a fully qualified assembly name that includes their version (either 4.0.0.0 or 4.1.0.0). You can probably use the 4.1 SDK to build either version but you would have to change the project references to point at a single version of Select DLLs at a time - and the...
- Tue Sep 20, 2016 5:50 pm
- Forum: Integration Development
- Topic: select 4.0 package on select 4.1
- Replies: 12
- Views: 1855
Re: select 4.0 package on select 4.1
Yes. Your package targeted version 4.0.0.0 of SoftPro's DLLs. You must now target the Select 4.1.0.0 DLLs by installing a 4.1 SDK and rebuilding the package. As long as you do not change your source (or package version number), you will not need a new package license.
- Tue Sep 20, 2016 5:37 pm
- Forum: Integration Development
- Topic: 4.1 API example for docs/reports
- Replies: 13
- Views: 2692
Re: 4.1 API example for docs/reports
Look out!!! As it turns out, even though an individual IRequest passed in through the IPrompt<PromptEventArgs> handler specifies that it is not required (IRequest.Required == false), it may still be required. If you are using the API to generate a report that has user generated values (checkboxes, ...
- Thu Sep 15, 2016 11:47 am
- Forum: Integration Development
- Topic: Phone Extensions
- Replies: 1
- Views: 486
Re: Phone Extensions
Phone, Fax, and Cell fields have two defined behaviors. If 7 or 10 number digits are entered, it will be automatically formatted to xxx-xxxx or (xxx)xxx-xxxx, respectively. Otherwise, these fields will hold up to 20 characters.
PhoneExtension fields hold up to 5 characters.
PhoneExtension fields hold up to 5 characters.