Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

UWS Change Log/Release Notes, Known Bugs
Ultidev Team
#1 Posted : Thursday, August 11, 2011 10:44:32 PM(UTC)
Ultidev Team

Groups: Administration
Joined: 11/3/2005(UTC)
Posts: 2,229

Thanks: 28 times
Was thanked: 53 time(s) in 52 post(s)
Change Log: (known bug information is below.)

Follow us on Twitter to be notified when the next release is out.

Build 21, March 8, 2015

  • Bug fix: Chunking functionality (streamed response) was not working properly.
  • Bug fix: Detection of whether system is running under Elevated user context was sometimes returning false negatives.


Build 20, January 11, 2014

  • Bug fix: Web apps running under UWS did not survive Windows upgrade, resulting in non-functioning apps and high CPU usage.
  • Bug fix: Attempts to install UWS on FIPS-enabled computers resulted in installation failure.
  • Bug fix: It was impossible to renew X.509 certificate that has already expired.
  • Bug fix: Using UWS Interactive Host as test web server in SharpDevelop caused UWS Interactive Host crash.


Build 19, May 25, 2013

  • Bug fix: Absence of Service Pack 2 for .NET Framework 2.0 caused system.missingmethodexception.
  • Bug fix: An attempt to register HTTPS endpoint using command line utility was producing hard-to-understand error message.
  • Bug fix: Attempts to create self-signed server certificate on Windows 8 was failing dues to problems with xenroll.dll registration.
  • Bug fix: On systems with .NET Framework 4.0 Client Profile, ASP.NET 4.x applications were allowed to get registered, but were fail to start because .NET Framework 4.0 Client Profile is missing components required for hosting web apps. ISVs shipping ASP.NET apps need to have .NET Framework 4.0 Full as a dependency.
  • Bug fix: Umlauts in AppReg parameter paths led to application registration failures.



Build 18, September 29, 2012.

  • Bug fix: WebDev Replacer utility was unable to determine WebDev folder correctly on some non-English systems, and as a result failed to do its job.
  • Bug fix: HTTP response generated by a web application was geting truncated to 512 byte in a very rare case when HTTP chunking is turned on at the very last moment by the Reponse.Write() method, like in the situation when web services has [WebMethod(BufferResponse = false)] attribute.
  • Bug fix: In UWS Explorer and UWS Interactive Server some web application "Navigate To" URLs were invalid on systems with non-English machine names.
  • Bug fix: When UWS serves requests, files containing certain characters like '+' and '&' were reported as not found or invalid.
  • Bug fix: Sometimes UWS installation failed due to xenroll.dll file prevented from being copied into System32 folder because it is sometimes protected by the system. Build 18 checks whether xenroll.dll exists before attempting to install and register it. Please note that starting with build 18, if target system has xenroll.dll file but it's not registered, UWS installer won't attempt to register it.
  • Bug fix: When UWS registered web application on a port for which Windows Firewall exceptions already exists, UWS replaced existing firewall exception with UWS's own. The fix keeps existing firewall exceptions - UWS will only create exceptions for ports that are not already open.
  • Bug fix: UWS fails to install on system with only .NET Framework 4.0 installed (and no .NET 2.0). The fix now directs users to the .NET 2.0 download page, when UWS installer runs in full UI mode. When UWS installer runs in reduced/passive/quiet UI mode, which is typical for installing it as a prerequisite, UWS installer will simply fail if .NET 2.0 is not installed. The solution is to have the bootstrapper of your web application installer check for .NET 2.0 (SP1 or later to be installed) on the target system before attempting to install UWS.


Build 17, May 9, 2012.

  • Bug fix: All but one Set-Cookie response headers were lost.

  • Change: Network Service user is granted read rights to application folder when application is registered.
  • Change: When response compression is turned on, large HTTP responses that were not compressed due to memory usage considerations. They are now compressed and chunk-encoded.

  • Enhancement: MIME types updated to include additional multimedia types, including m4a, ogg and a few others.


Build 16, April 15, 2012.

  • Bug fix: Basic authentication was not working properly.
  • Bug fix: on some systems loading HTTP.SYS SSL configuration failed and lead to crash.
  • Bug fix: Interactive host sometimes crashed while trying to read memory usage performance counter data.

  • Change: made server variables more consistent with IIS.
  • Change: application authentication type selection is now an exclusive choice (radio button), vs. multiple choice (checkboxes) in the past. Authentication types that had Anonymous in it became anonymous.
  • Change: Responsiveness of UWS Explorer improved, specially when service and hosts are not running.
  • Change: Granting "Network Service" user access to ASP.NET directories now occurs during application registration instead of at UWS installation, so that even if .NET Framework is installed after UWS, its folders would be ACLed.

  • New Feature: "ASP.NET Web Site Administration Tool" can now be started from UWS Explorer or UWS Interactive Host.



Build 15, February 28, 2012.

  • Change: To uninstall UWS use "Uninstall UltiDev Web Server Pro" menu item from UWS Programs menu. New uninstallation routine displays list of applications currently hosted by UWS, giving users a chance to see which web applications will stop working in case UWS is uninstalled. Ability to uninstall UWS from "Add/Remove Programs" and "Programs and Features" has been removed.
  • Change: At the end of stand-alone (full UI) installation of UWS, the UWS Explorer application management console is launched. This change does not affect cases when UWS installer is bundled as "passive", "quiet" or otherwise reduced-UI package, meaning UWS Explorer won't pop up in the process of your application installation.

  • New feature: added SSL/TLS support and Certificate Management. UWS can allows creating and managing X.509 digital certificates, both self-signed and production-level CA-signed ones.
  • New feature: simplified or automatic creation of desktop shortcuts to redistributable web applications when applications are registered with UWS. This significantly simplifies web application installation authoring.
  • New feature: launch your web application in the browser right after installation using "/autostart" parameter of UWS.RegApp.exe. There is a corresponding programmatic way to do the same using .NET and COM APIs.

  • Bug fix: Request process logic changed to let ASP.NET pipeline try to handle requests with no physical files mapped to the URL, before returning 404. This allows HttpHandlers to process requests that may look like potential 404.
  • Bug fix: UWS Explorer crashed when selected host process used more 2GB of RAM.
  • Bug fix: During application registration, taken listen-to URLs were not filtered out if Vdir was specified (non-"/").



Build 14, December 4, 2011

  • Bug Fix: upgrade installation was failing with "Unable to load assembly" error message. The bug was introduced in build 13.


Build 13, December 3, 2011

  • Installation problems related to COM+ application catalog are eliminated by moving components into windows services.
  • Added Windows Explorer-like file management control to application settings manager in UWS Explorer.
  • Added ability to host a web application in UWS Interactive Host by right-clicking a folder in Windows Explorer.


Build 12, October 31, 2011

  • New feature: Advanced Installer (AI) support with adding UWS as a prerequisite and documentation for creating AI installation incorporating UWS.
  • Bug fix: Clients using UWS.Configuration API were referencing configuration assembly of a specific version, making any program using configuration API fail when a newer version of UWS is installed.
  • Bug fix: Virtual folder names containing white spaces resulted in 404 page not found.
  • Bug fix: UWS installation failed when port 7756 is unavailable.
  • Bug fix: Windows firewall exceptions were not having any effect.


Build 11, October 9, 2011

  • Started supporting scripts in /aspnet_client, but for now support is limited for applications that are at the root, not in a virtual directory.
  • Bug fix: UWS would not install on some international versions of Windows.
  • Default settings for UWS Interactive Host have changed when it's running as a Visual Studio development server. UWS Interactive Host in WebDev mode runs by default as if with "/BROWSER=nobrowser" and "/dirbrowsing=yes" command line switches.
  • Bug fix: UWS Interactive Host sometimes quits when launched by Visual Studio with "nodirlist" command line parameter.
  • Bug fix: UWS Explorer application management console was producing "ding" sound when green text screen was scrolling.
  • Bug fix: In UWS Explorer application management console it was possible to start adding static HTML site to a host that is ineligible for hosting static HTML web applications.


Build 10, Sept 24, 2011

  • Bug fix: All but one Set-Cookie response headers were lost.
  • Bug fix: system.missingmethodexception thrown if .NET Framework SP2 not installed.
  • Enhancement: Added a new command line parameter to UWS.RegApp.exe allowing dynamic extension specifications by application installers.
  • Bug fix: UWS Explorer sometimes won't start on Vista/Win7/2008 complaining it requires user elevation.
  • Bux fix: Intermittent PerfCounters exception error shown when selecting a host node in UWS Explorer.
  • Bug fix: Process handling threads impersonate process user for Anonymous auth, to ensure applications' Request.LogonUserIdentity is not null.


Build 9, Sept 7, 2011

  • Added support for InstallShield. UWS installs itself as an InstallShield prerequisite.
  • Ability to replace Visual Studio internal development web server (WebDev.WebServer) with UWS as an integrated debugging web server with a couple of mouse clicks.
  • Bug fix: MVC and other HttpHandler-based requests were not always served properly.
  • Bug fix: In UWS Explorer it was possible to move a web site/app to a private host processes.
  • Bug fix: Legacy UltiDevCassiniServerConfiguration.dll was not properly registered in GAC during upgrade installation, causing UWS COM API registration calls to fail.
  • Bug fix: In UWS Explorer App Registration Wizard default host was not selected by default.


Build 8, Aug 11, 2011

  • Updated MIME types for cache manifest.
  • Bug fix: Assigning port 0 when registering an app was adding new listen url with every registration attempt.


Build 7, Aug 7, 2011

  • Updated diagnostics for UWS.AppHost EXEs to allow tracing.
  • Made AppLocator web app capable of using pathinfo instead of query string for redirectring. Also made possible redirecting to any doc in any app subfolder - not just to default doc.
  • Bug fix: default document prohibits illegal characters.
  • Interactive Server program now listens to external IPs when run as Administrator (on XP/2003) and Elevated Admin on (on Vista/7/2008).
  • Added context menu to application treeview nodes in UWS Explorer.
  • Added context menu to host process treeview nodes in UWS Explorer. Added ability to create new apps in the selected host.
  • Important bug fix: eliminated downtime when ASP.NET AppDomain is unloaded due to configuration/folder content changes.


Build 5, July 10, 2011
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
1 user thanked Ultidev Team for this useful post.
JeremyMeeks on 1/5/2017(UTC)
Ultidev Team
#2 Posted : Saturday, August 13, 2011 11:38:41 AM(UTC)
Ultidev Team

Groups: Administration
Joined: 11/3/2005(UTC)
Posts: 2,229

Thanks: 28 times
Was thanked: 53 time(s) in 52 post(s)
Known Bugs:

Build 20:

  • Small memory leak found in the PInvoke used to detect whether system is running Elevated. Fixed in build 21.
  • Detection of whether the system is running Evelated sometimes returned false negatived. Fixed in build 21.

Build 19:

  • UWS Interactive Server crashes when launched by SharpDevelop. Will be fixed in build 20.
  • SSL certificate renewal fails if certificate has already expired. Will be fixed in build 20. Workaround: renew certificate before it has expired.
  • UWS stop working, and CPU usage goes up, after Windows upgraded to 8.1. Workaround is here. Will be fixed in build 20.


Build 18:

  • Reintroduced bug: absence of Service Pack 2 for .NET Framework 2.0 causes system.missingmethodexception. The workaround is to install Service Pack 2 for .NET Framework 2.0. Will be fixed in the next released.
  • An attempt to register HTTPS endpoint using command line utility displays hard-to-understand error message.
  • Attempts to create self-signed server certificate on Windows 8 was failing dues to problems with xenroll.dll registration. Work-around: use regsvr32 to register xenroll.dll manually.
  • On systems with .NET Framework 4.0 Client Profile, ASP.NET 4.x applications were allowed to get registered but would fail to start because .NET Framework 4.0 Client Profile is missing components required for hosting web apps. ISVs shipping ASP.NET apps need to have .NET Framework 4.0 Full as a dependency.
  • Umlauts in AppReg parameter paths lead to application registration failures.
  • Chunked (streamed, unbufferred) HTTP responses were not returned rendered correctly. Fixed in build 21.


Build 17:

  • WebDev Replacer utility cannot determine WebDev folder correctly on some non-English systems, and as a result fails to do its job. Will be fixed in the release.
  • HTTP response generated by a web application gets truncated to 512 byte if a very rare case when HTTP chunking is turned on at the very last moment by the Reponse.Write() method, like in the situation when web services has [WebMethod(BufferResponse = false)] attribute. Will be fixed in the next release.
  • In UWS Explorer and UWS Interactive Server some web application "Navigate To" URLs may be invalid on systems with non-English machine names. Will be fixed in the next release.
  • When UWS serves requests, files containing certain characters like '+' and '&' were reported as not found or invalid. Will be fixed in build 18.
  • Sometimes UWS installation fails due to xenroll.dll cannot be copied into System32 folder as it is sometimes protected by the system. Next release checks whether xenroll.dll exists before attempting to install and register it. Please note that starting with build 18, if target system has xenroll.dll file but it's not registered, UWS installer won't attempt to register it.
  • Sometimes "Keyset does not exist while acquiring provider context" error is displayed when creating self-signed SSL certificate. Workaround: delete UWS signing certificate named "Do not trust..." from machine's Trusted Root Certificates store and try again.
  • When UWS registers web application on a port for which Windows Firewall exceptions already exists, UWS replaces existing firewall exception with UWS's own. This will be fixed in the next release: existing firewall rules won't be replaced by UWS - UWS will only create exceptions for ports that are not already open.
  • UWS fails to install on system with only .NET Framework 4.0 installed (and no .NET 2.0). Workaround: install .NET Framework 2.0. Dependency on .NET Framework 2.0 will be reinstated in the next release.
  • SSL on Windows XP is not working properly out of the box. Workaround (proceed at your own risk): on the XP system in question delete 30 or more trusted root certificates that you are sure are not going to be used. Possibility of fix is being investigated.



Build 16:

  • All but one Set-Cookie response headers were lost.. Workaround: use previous build. Will be fixed in the next release.



Build 14:

  • During application registration, taken listen-to URLs are not filtered out if VDIR is specified (non-"/"). Workaround: don't use virtual directory or use different virtual directory. Will be fixed in the next release.


Build 13:

  • Upgrade installation fails. Introduced in this build.


Build 12:

  • Small minority of users affected by various installation issues related to COM+. Reliance on COM+ will be eliminated in the next build.


Build 11:

  • Requested URLs with whitespaces in folder names get 404 or an error. Will be fixed in the next released.
  • Application installers using UWS.Configuration API fail after UWS gets upgraded. Version-dependent reference to UWS.Configuration makes installer UWS version-dependent, and thus breaks after UWS is upgraded. Work-around: use UWS.AppReg.exe utility for now. The problem will be fixed in next release.
  • Windows firewall exceptions are not created properly, preventing UWS from being accessible on some systems. Workaround: create exceptions manually for EXEs named UWS.AppHost.ClrX.xxxxx.exe from "C:\Program Files (x86)\UltiDev\Web Server" folder. Will be fixed in the next release.


Build 10:

  • Installation fails on some non-English versions of Windows due to "appid" parameter being incorrectly lower-cased. To work around switch Windows to an English-based locale. The problem will be fixed in the next build.
  • Scripts in the "/aspnet_client/system_web/" folders are not accessible. Will be fixed in the upcoming version, but the fix will be limited to site root applications - those with "/" virtual directory. Complete resolution will be available in future releases.
  • When UWS Interactive Host replaces Visual Studio WebDev.WebServer, it fails to run complaining about not recognizing "nodirlist" parameter. There is no workaround. Will be resolved in the next release.


Buid 9:

  • Absence of Service Pack 2 for .NET Framework 2.0 causes system.missingmethodexception. The workaround is to install Service Pack 2 for .NET Framework 2.0. Will be fixed in the next released.
  • A terrible one: .NET Framework bug allows only one Set-Cookies header in the response. Will be fixed in the next build. There is no work-around.
  • Request.LogonUserIdentity is null with Anonymous authentication. Under IIS and WebDev Request.LogonUserIdentity is never null. Will be fixed in the next build. To work around use Negotiate or NTML authentication.
  • On Vista/Win7/2008 UWS Explorer sometimes complains it's not running elevated when it is. Fixed in the next build.


Buid 8:

  • Upgrade installation causes COM API to fail on systems earlier than Windows 7/2008 R2, when used by 3rd parties to register/unregister applications. .NET API is not affected. Work-around: uninstall previous version, then install the new one.
  • Sometimes requests processed by an HttpHandler get "stuck"/hanging without returning anything to the client. This problem affects mostly ASP.NET MVC applications. There is no workaround. It will be resolved in the next release.
  • In UWS Explorer it's possible to move a web site/app to a private host process.
  • In UWS Explorer application registration wizard default host process is not selected. New host is offered as a default choice.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Rss Feed  Atom Feed
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You can vote in polls in this forum.