Release Bulletin for SnapDevelop (PB Edition) 2019
Make sure your system meets all requirements before you install SnapDevelop (PB Edition) 2019.
Windows 10, Windows 8.1, or Windows 7 SP1
Universal C Runtime
The setup program will check if Universal C Runtime is installed; if it is not installed, the setup program will provide the package list, and you will need to manually download and install the package. Or you can follow the instructions in Installation Guide.
Microsoft .NET Framework 4.6.1 SDK (can be installed during the SnapDevelop installation progress)
Microsoft .NET Core SDK 2.1.6 (can be installed during the SnapDevelop installation progress)
TypeScript SDK 3.1 (can be installed during the SnapDevelop installation progress)
SnapDevelop (PB Edition) 2019 has the following known issues.
- Random errors or crashes may happen with the editor.
- User experience of coloring, auto-filling, syntax detecting etc. needs further improvements, for example, some code may not be colored properly.
- It is unsupported to dynamically modify a value in the debugger.
- User experience of debugging needs further improvements, for example,
- The exception dialog box appears even though the exception is captured by Try Catch.
- It is unsupported to write an expression using dot notation in Quick Watch.
- The debugger failed to show the file and the cursor failed to stop at the script when debugging an error in the SnapDevelop application.
- During the debugging process, the debugger console failed to activate and show at the front automatically, unless it is clicked.
- When using DataTips to view the object data, it may falsely report an object as not instantiated.
- When a console app downloaded XUnit from Nuget, debugger could not work and reported the error “Unable to run or debug the unit test projects”.
- Go To Implementation sometimes cannot go to the exact location.
- Performance with large apps needs further evaluations and improvements.
- When modifying a long list of properties at one time, as the user scrolls the list the modified properties that have scrolled off the screen will lose its change.
- SnapDevelop does not support publishing an API to the server via FTP, or to a server running the cloud or Docker.
- When SnapDevelop publishes an API, it requires that the server disable the firewall.
- The Web Deploy plug-in required for publishing project must be installed in full installation mode to ensure successful publishings.
- If you sign an ASP.Net Core Web API project using a pfx key file, the project cannot be deployed successfully.
- The XUnit ITestOutputHelp interface failed to show the execution result of a unit test.
- The following syntax or item is unsupported to run against unit tests:
- Reference to data via Memberdata, for example, MemberData(nameof(XunitDataList.intconvert), MemberType = typeof(XunitDataList))
- Customized attributes for [XunitDatas]
- displayname property
- Parameter that uses params (no result will be shown)
- Test points of the .NET Framework application (SnapDevelop does not support .NET Framework app currently)
- Some runtime DLL files (as well as all user DLLs) are not digitally signed, such as Oracle.ManagedDataAccess.dll (3rd-party), Npgsql.dll (3rd-party), SnapDevelop.xUnit.Runner.dll.
- Cursor position is not remembered when switching between the CS file editors.
Offline Nuget packages:
Offline Nuget packages may not be fully supported, for example:
- It may not be always successful to use or update the Nuget packages in the offline environment, in such case, online environment (with access to www.nuget.org) is recommended.
- It is unsupported to install or update a Nuget package offline in Windows 7 environment.
SVN & Git Known Issues:
- After you enable SnapDevelop SVN or SnapDevelop Git source control for a solution, it is not possible to disable it or switch to another source control option.
SVN Known Issues:
- In SnapDevelop IDE, the file "modify" and "add" statuses use the same icon, so the statuses cannot be easily differentiated.
- If a file is set to need-lock, you cannot save the file successfully, but there is no warning message for it.
- The Add Solution to Subversion wizard checks the validity of all inputs at the last step. Therefore if you make a mistake at the first step, you won't know it till the last step.
- SnapDevelop IDE may be sent to back after one of these SVN operations: Merge, Switch, Branch, Mark as Resolve.
- After editing or resolving conflicts in a .NET Framework project, the project and files may display incorrect statuses. The issue can be fixed by reopening the project.
- Temporary files resulted from conflicts are added into the file list, with "add" status in Solution Explorer. Users must pay attention not to commit these temporary files to the remote repository.
Git Known Issues:
- Double-clicking a project in the Local Git Repositories list won't take effect (the expected behavior is that the project shall open).
- The New and Add functions provided in the Local Git Repositories do not work properly yet. For example, if you specify a directory to add, the directory is directly added to the list, no matter whether the directory is a project folder, or whether the directory contains several projects; The projects added to the Local Git Repositories list are not sorted alphabetically.
- The local Git repository does not automatically create a folder that maps to the folder of the destination repository that you are cloning to in the Connections.
- If you click the Git Remove right-mouse menu item, the current project will be removed from the solution.
- The URL you enter for a Git push won't be validated.
- The Git repository account you add in the Connections won't be validated.
- The Local Git Repository account you add in the Connections won't be validated.
- Some output messages may be duplicated for the Git fetch operation.
- There are no statistics on the completed objects/total files when you perform a Git push.
- There is no indicating information on whether, and how many, files shall be pushed to the remote repository.
Upgrade Notes for Beta Users
Please pay attention to the following important notes when you upgrade to the GA build:
When you launch Appeon Installer to install the build, you can use the Update button to directly update the beta version (1 or 2) to the current build.
The version of NuGet package (SnapObjects.Data, PowerBuilder.Data, etc.) is changed to 1.0.x.
There are a few major renaming and re-factorings in the runtime libraries:
DataStore is no longer part of SnapObjects.PowerBuilder.Data, instead, it belongs to PowerBuilder.Data
SnapObjects.Data.ClientSync.AspNetCore is renamed as SnapObjects.Data.AspNetCore
PowerBuilder.Data.ClientSync.AspNetCore is renamed as PowerBuilder.Data.AspNetCore
ModelMapper is now renamed as SqlModelMapper
If you have used SnapDevelop and SnapObjects for developing C# projects with the earlier beta, you must perform the following steps for smooth migration to the GA build:
- Go to Tools -> Options -> Nuget Package Manager and click the Clear All NuGet Cache(s) button to clear the NuGet caches in SnapDevelop.
- Back to the Solution Explorer, on the right-click menu click Clear Solution.
- Then on the right-click menu click Rebuild Solution.
- Thoroughly check the scripts in existing C# solutions, and make sure the references to the runtime libraries are updated correspondingly.
Previously after you generate a model from DataWindow, a .pbw file is created for storing configuration information. Now the file suffix is changed to .pbwconfig.
New ODBC library provided for connecting to SQL Anywhere. Although theoretically should work for any DB, we have only extensively tested against SQL Anywhere.
When you see the error message that asks you check "Whether the Copy to Output Directory property of the DataWindow file is specified", set the Copy to Output Directory of the DataContext file to "Copy always" or "Copy if newer".
Third-Party Components and Deployment
SnapDevelop applications have some dependencies on third-party components that are installed with SnapDevelop.
List of Free Download Components (Including Open Source Components)
For the complete list of the free download components (including open-source components), view the Free Download Terms document on the Appeon Web site.