 Revision news |
|
| |
|
| Version 1.1.8 |
Remove 1 bug: ( ** only re-apply )
I find a problem on the replace functions. When referring to a txtbox to "replace" txt (using the replace syntax #txtBox# as txbox@_form_@), the line breaks do not appear in the email. This version fix the bug |
| |
|
| Version 1.1.7 |
Remove 1 bug: ( ** only re-apply )
I find a problem on the redirect behavior when the upload file size is more the limit |
| |
|
| Version 1.1.6 |
Remove 1 bug: ( ** only re-apply ) |
| |
When you have a Sql to create a DatSet in the extension panel and you have a single apex (') delimiter in the Sql string the Asp.Net return the error: " Parser Error Message: The server tag is not well formed.". The new release remove this bug |
| |
|
| Version 1.1.5 |
Remove 1 bug: ( ** only re-apply ) |
| |
When you use Asp.Net validator don't recognize the "Not Page.IsValid" and in case the page contains error (not valid validation) the mail is send. The new release remove this bug |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| What you must do in the 2 different case to update the extension code in existing pages: |
|
| * complete restore |
To apply this new features in an exixting page you must remove all the code of the old version and re-apply the extension. This because in this new release I modify the code inserted in the page to add new parameters and in this case DW don't recognize the old code and is unable to detect the extension in the page. |
| |
|
| ** only re-apply |
To apply this new features in an existing page you must only double-click on the extension label in the server behavior panel, and after the extension panel is open click on the Ok button.
This will update all the files in the AspNetMailFiles and in the bin folder and the new features will be available. |
| |
|
Every time you upgrade to a new release don't forget to upload
on the server all the AspNetMailFiles folder that contains the new files. |
