On this page:
- 1.0.17
- 1.0.16
- 1.0.15
- 1.0.14
- 1.0.13
- 1.0.12
- 1.0.11
- 1.0.10
- 1.0.9
- 1.0.8
- 1.0.7
- 1.0.6
- 1.0.5
- 1.0.4
- 1.0.3
- Resolved issues
- Changes in results post upgrade
- DOTNET-482 - Avoid using Parse for primitive types and used instead TryParse - 8150
- DOTNET-488 - Avoid instantiations inside loops - 7212
- DOTNET-489 - Links created from .NET method "A" to .NET method "B" which all have the same name
- DOTNET-492 - The exception Exception should never been thrown. Always Subclass Exception and throw the subclassed Classes - 7824
- 1.0.2
- 1.0.1
- 1.0.0
1.0.17
Resolved issues
| Internal ID | Call ID | Summary | Impact? |
|---|---|---|---|
| DOTNET-969 | - | SSL in .Net extension | A change has been implemented in preparation for the future support of encrypted SSL connections to CAST Storage Service/PostgreSQL. |
1.0.16
Resolved issues
| Internal ID | Call ID | Summary | Impact? |
|---|---|---|---|
| DOTNET-905 | - | FALSE violation for Avoid using Keywords as names | Following rule: 'Avoid using Keywords as names' has been disabled in 1.0.16. So, after upgrading to 1.0.16, this rule is no longer triggered during an analysis. |
1.0.15
Resolved issues
| Internal ID | Call ID | Summary | Impact? |
|---|---|---|---|
| DOTNET-612 | - | Missing devirtualization links when type instantiations are involved | Devirtualization links are now created properly in the context of type instantiations. Therefore after an upgrade to this version of the extension and the generation of a post upgrade consistency snapshot, results may change: more accurate transaction information will be produced. |
| DOTNET-876 | 19086,19229 | Snapshot error - ‘Error while executing Procedure’ | After upgrading to 1.0.15, no error is displayed. |
1.0.14
Resolved issues
| Internal ID | Call ID | Summary | Impact? |
|---|---|---|---|
| DOTNET-842 | - | Report - Devirtualization should create a link to all overrides at least | After the fix, when the devirtualization fails to find the actual types on which a virtual call is made, then links are drawn to all overrides instead of drawing no link at all. |
1.0.13
Resolved issues
| Internal ID | Call ID | Summary | Impact? |
|---|---|---|---|
| DOTNET-742 | 17909 | FALSE VIOLATION FOR RULE- "Close the outermost stream ASAP" | It fixes false violations for the quality rule. Results may be impacted when re-analyzing existing source code with this release of the extension. |
| DOTNET-789 | - | There should be fatal error instead Warning message "Analysis failure, could not load a type. The following assemblies could not be loaded as well:" | After the fix, 'Fatal error' message is displayed. |
DOTNET-818 | 17666 | Porting Task - Perm Fix: FALSE VIOLATIONS FOR "Avoid improper processing of the execution status of data handling operations" | It fixes false violations for the quality rule. Results may be impacted when re-analyzing existing source code with this release of the extension. |
| DOTNET-820 | - | DOTNET.0020:Error while processing visitor: WebServiceVisitor | After the fix, no error while processing visitor. |
1.0.12
Resolved issues
Internal ID | Call ID | Summary | Impact? |
|---|---|---|---|
| DOTNET-763 | 18245 | "LOC increases post migration" | Empty lines in code are not counted after this update. Hence you will see decrease in LOC after the upgradation. |
1.0.11
Resolved issues
| Internal ID | Call ID | Summary | Impact? |
|---|---|---|---|
| DOTNET-621 | - | Bug in the quality rule "avoid instantiations inside loops" | Accurate results. More conditions have been added for the violations to be raised. |
| DOTNET-718 | 17275 | Permanent Fix: FALSE VIOLATION FOR RULE- Close the outermost stream ASAP | It fixes false violations for the quality rule. Results may be impacted when re-analyzing existing source code with this release of the extension. |
| DOTNET-745 | - | Regression: Snapshot failed with ERROR: duplicate key value violates unique constraint "dss_objects_pk" | Snapshot can be taken without any error in AIP 8.3.13 |
1.0.10
Resolved issues
| Internal ID | Call ID | Summary | Impact? |
|---|---|---|---|
| DOTNET-689 | 16402 | Performance issue when analyzing application | Time required to run an analysis should now be improved. No impact to results. This bug was seen only in the specific case of relatively large projects containing numerous dependencies between their objects. In this specific context, a lot of time was spent in the garbage collector (sometimes many hours) causing analysis duration to be excessive. |
DOTNET-722 | 17509 | PERMANENT FIX- AIP recommends to declare as static methods that cannot be declared as static | In previous releases of the extension, false positive violations to the rule "Declare as Static all methods not using instance members (.NET) - 7270" were returned during the analysis. The false violations were detected in property getter and setters, which cannot be declared static when they are overridden by a class from a base class, or when a class implements them from an interface. This bug has now been fixed and therefore after an upgrade to the current version of the extension and the generation of a post-upgrade consistency snapshot, results may changed for this rule - less false violations providing more accuracy. |
1.0.9
Updates
DOTNET-636 - PostgreSQL connectivity
A change has been implemented to introduce a connectivity layer compatible with PostgreSQL 10 and 11.
1.0.8
Resolved issues
| Internal ID | Call ID | Summary | Impact? |
|---|---|---|---|
DOTNET-634 | 15799 | FALSE VIOLATION FOR RULE- Close the outermost stream ASAP | It fixes false violations for the quality rule. Results may be impacted when re-analysing existing source code with this release of the extension. |
1.0.7
Resolved issues
Internal ID | Call ID | Summary | Impact? |
|---|---|---|---|
| DOTNET-665 | 15662 | Performance issue with devirtualization in .NET analysis | .NET analysis should be able to finish at a logical pace in regards to the application size |
1.0.6
Updates
DOTNET-651
Metrics are no longer calculated for generated objects, as such, analysis results may be impacted.
Resolved issues
| Internal ID | Call ID | Summary | Impact? |
|---|---|---|---|
| DOTNET-568 | 14692 | Asmx files are not saved in some cases | After upgrading to 1.0.6, .asmx files will be correctly analyzed. As such, analysis results may be impacted. |
| DOTNET-629 | 15751 | Permanent Fix - FALSE VIOLATION FOR RULE- Declare as static all methods not using instance members | In previous releases of the extension, violations of this rule were being incorrectly returned for interfaces. After upgrading to 1.0.6, no violations will be reported in interfaces. As such, analysis results may be impacted. |
| DOTNET-635 | - | Wrong line of code count. | After upgrading to 1.0.6, the line of code count will be correct. |
| DOTNET-647 | 13903 | Permanent Fix: "GUID duplicate found : CAST_DotNet_SOAP_Proxy" | After upgrading to 1.0.6, the warning will not occur. |
1.0.5
Resolved issues
Internal ID | Call ID | Summary | Impact? |
|---|---|---|---|
| DOTNET-10 | - | Duplicate GUID issue while analyzing Application App4. | - |
| DOTNET-498 | 13496 | CastGenerated objects created from aspx files are marked as internal. | - |
| DOTNET-533 | 13933 | "The Type or Namespace name "XX" could not be found" warning. | Warning message has been removed. |
| DOTNET-592, DOTNET-600 | 14997, 15002 | Missing links from C# to Database objects through constants. | Links are now generated correctly. Results may be impacted when re-analysing existing source code with this release of the extension. |
| DOTNET-624 | 14824 | .NET warning: System.AggregateException: One or more errors occurred. System.NullReferenceException: Object reference not set to an instance of an obj | Warning messages have been removed. |
1.0.4
Resolved issues
Internal ID | Call ID | Summary | Impact? |
|---|---|---|---|
| DOTNET-527 | 13802 | DOTNET.0003:Unknown exception System.AggregateException: One or more errors occurred. ---> System.ArgumentException: An item with the same key has alr | Analysis will now run without failing. |
| DOTNET-529 | 4498 | Standard javascript library files are not being excluded from the .Net Analysis | In previous releases of the extension, when using the "Exclude standard Javascript Libraries" option in the CAST Management Studio, violations were still being raised on objects that should have been excluded. This bug has now been fixed and therefore after an upgrade to this release of the extension and the generation of a post upgrade consistency snapshot on unchanged source code, results may be impacted: objects are now correctly excluded and violations are no longer raised on them. |
| DOTNET-546 | 14244 | False positives for C# rule "Avoid using Keywords as names" | In previous releases of the extension, false positive violations were being raised for the C# rule "Avoid using Keywords as names - 3570". Violations were being incorrectly raised for words that were not keywords. This bug has now been fixed and therefore after an upgrade to this release of the extension and the generation of a post upgrade consistency snapshot on unchanged source code, results may be impacted: less false violations and more accurate results. |
| DOTNET-564 | 14533 | False violation - Avoid Unreferenced Methods | In previous releases of the extension, false positive violations were being raised for the rule "Avoid Unreferenced Methods - 7908". This bug has now been fixed and therefore after an upgrade to this release of the extension and the generation of a post upgrade consistency snapshot on unchanged source code, results may be impacted: less false violations and more accurate results. |
1.0.3
Resolved issues
Internal ID | Call ID | Summary | Notes |
|---|---|---|---|
| DOTNET-482 | 13330 | False Positive for rule : "Avoid using Parse for primitive types and used instead TryParse" | See information below. |
| DOTNET-488 | 12889 | False positive for rule: "Avoid instantiations inside loops" | See information below. |
| DOTNET-489 | 11019 | So many static links are getting created from a .NET method to several other .NET methods with same name, creating a large SCC group. | See information below. |
| DOTNET-490 | 12883 | .Net code analysis running slow | - |
| DOTNET-492 | 13252 | False violations for "The exception Exception should never been thrown. Always Subclass Exception and throw the subclassed Classes" | See information below. |
| DOTNET-497 | - | Crash in CastIlCS.dll during the devirtualization | - |
Changes in results post upgrade
This section lists changes in results post upgrade from 1.0.2 to 1.0.3:
DOTNET-482 - Avoid using Parse for primitive types and used instead TryParse - 8150
A bug has been discovered that is causing the rule "Avoid using Parse for primitive types and used instead TryParse - 8150" to be incorrectly violated when a Parse is NOT used within a try catch block. This bug has been fixed and therefore after an upgrade to 1.0.3 and the generation of a post upgrade snapshot on the same source code, results may change: there may be less violations for this rule, improving accuracy.
DOTNET-488 - Avoid instantiations inside loops - 7212
A bug has been discovered that is causing the rule "Avoid instantiations inside loops - 7212" to be incorrectly violated where an initializer (for / foreach) is present in a loop. This bug has been fixed and therefore after an upgrade to 1.0.3 and the generation of a post upgrade snapshot on the same source code, results may change: there may be less violations for this rule, improving accuracy.
DOTNET-489 - Links created from .NET method "A" to .NET method "B" which all have the same name
A change has been made in the way the .NET analyzer behaves with regard to links between .NET methods which cannot absolutely be determined. Previously the .NET analyzer would create multiple objects of the same name for one single .NET method "B" and create links from the calling .NET method "A" to those objects. This resulted in multiple links between .NET method "A" and multiple instances of .NET method "B". This behaviour has now been changed: multiple instances of objects will still be created, however, only one link between the methods will be created. Therefore, after an upgrade to 1.0.3 and the generation of a post upgrade snapshot on the same snapshot, results may differ: there may be less links between objects affecting transaction values.
DOTNET-492 - The exception Exception should never been thrown. Always Subclass Exception and throw the subclassed Classes - 7824
A bug has been discovered that is causing the rule "The exception Exception should never been thrown. Always Subclass Exception and throw the subclassed Classes - 7824" to be incorrectly violated. This bug has been fixed and therefore after an upgrade to 1.0.3 and the generation of a post upgrade snapshot on the same source code, results may change: there may be less violations for this rule, improving accuracy.
1.0.2
Resolved issues
Internal ID | Call ID | Summary |
|---|---|---|
| DOTNET-466 | - | False violation appearing for the QR: "Close the outermost stream ASAP" |
| DOTNET-468 | 12486 | False Violation for QR - Close SQL connection ASAP |
Changes in results post upgrade
This section lists changes in results post upgrade from 1.0. to 1.0.2:
DOTNET-466 - Close the outermost stream ASAP - 8108
A bug has been discovered that is causing the rule "Close the outermost stream ASAP - 8108" to be incorrectly violated when the stream is closed in a "finally block". This bug has been fixed and therefore after an upgrade to 1.0.2 and the generation of a new snapshot on the same source code, results may change: there may be less violations for this rule, improving accuracy.
DOTNET-468 - Close SQL connection ASAP - 3612
A bug has been discovered that is causing the rule "Close SQL connection ASAP - 3612" to be incorrectly violated when the SQL connection is correctly closed. This bug has been fixed and therefore after an upgrade to 1.0.2 and the generation of a new snapshot on the same source code, results may change: there may be less violations for this rule, improving accuracy.
1.0.1
Resolved issues
Internal ID | Call ID | Summary |
|---|---|---|
| DOTNET-47 | Duplicate GUID warnings on Dataflow test case | |
| DOTNET-53 | Regression: Warnings : Unable to open file "ExtensionExternalLinksRules.xml" after migration from 8.3.2->8.3.4 |
1.0.0
Changes in results post upgrade
This section lists changes in results post upgrade from CAST AIP 8.3.2 with the embedded .NET Analyzer.
Externalization of the .NET Analyzer
The .NET Analyzer has been "externalized" as an official CAST AIP Extension in this release of CAST AIP. This extension is delivered and installed automatically with CAST AIP 8.3.x with new CAST AIP triplets and as part of an upgrade. Note that any changes in analysis results that are visible after an upgrade to CAST AIP 8.3.x (and therefore to the externalized .NET Analyzer) are only due to improvements and bug fixes introduced in this release of the analyzer and NOT due to the externalization.
SCRAIP-30874 - Declare as Static all methods not using instance members - 7270
A bug has been discovered that is causing inconsistent results for the Quality Rule "Declare as Static all methods not using instance members - 7270". This bug has now been fixed, therefore after an upgrade to CAST AIP 8.3.3 (from CAST AIP 8.3.2) and the generation of a post upgrade snapshot on the same source code, results may differ.
