Display: Cloud | List
Most Popular Tags
Results (62 total) All > productbug (x)
Possible Bug Associated with Application.OpenForms (Application.OpenForms Property (System.Windows.Forms))
There is a nasty bug in the implementation of Application.OpenForms, you should avoid relying on it. This code shows the bug at work:Public Class Form1    Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click        Me.ShowInTaskbar = Not Me.ShowInTaskbar
Last modified by Thomas Lee on 7/6/2011 1:28:24 PM
Tags:  productbug
Bug in the argument validation of the WriteEntry method (EventLog.WriteEntry Method (String, String, EventLogEntryType, Int32) (System.Diagnostics))
The method checks if the message has over characters 32766 and throw an ArgumentException: “The message string is longer than 32766 bytes.” if is over this limit. However it looks like the underlying method ReportEvent in advapi32.dll is expecting the max length to be the byte count of the string encoded as Unicode. So even if the string is under 32766 characters you will receive an exception th
Last modified by Thomas Lee on 6/19/2011 7:25:47 PM
Tags:  productbug
Adding is simple - deleting can be a bit more painful. (SPFieldCollection.AddDependentLookup Method (Microsoft.SharePoint))
See http://www.chaholl.com/archive/2011/02/02/sharepoint-2010-bug-the-primary-lookup-field-cannot-be-deleted.aspx Deleting dependent lookups in custom field controls doesn't work properly without some tweaking
Last modified by Thomas Lee on 2/13/2011 5:37:43 PM
Tags:  productbug
Product bug (SetArcDirection function (Windows))
If you record into an EMF DC, SetArcDirection() call seems to be buffered in the Arc() call, and if you do the following sequence: SaveDC() SetArcDirection(,AD_CLOCKWISE) Arc(...) RestoreDC() SaveDC() SetArcDirection(,AD_CLOCKWISE) Arc(...) RestoreDC() then the second SetArcDirection() is ignored (which is false, as the RestoreDC() sets it to COUNTERCLOCKWISE internally during PlayEnhMeta
Last modified by Thomas Lee on 2/13/2011 5:37:26 PM
beware of an implementation bug (Rectangle.IntersectsWith Method (System.Drawing))
The way MS implemented this method does not detect intersections if they occur on the edge of the rectangle. for example the following intersection test returns false: rectangle (0,0)-(10,10) does not intersect with rectangle (0,0)-(0,0)
Last modified by Thomas Lee on 2/13/2011 5:36:38 PM
Tags:  productbug
This method appears to return an HttpWebRequest using the client stack (WebRequest.CreateHttp Method (String) (System.Net))
It appears that the HttpWebRequest class that is returned by this method when you supply a http or https url is using the client stack, even though you may not have made a call to http://msdn.microsoft.com/en-us/library/system.net.webrequest.registerprefix.aspx. The Create method (http://msdn.microsoft.com/en-us/library/0aa3d588(VS.95).aspx) appears to return the WebRequest using the appropriate
Last modified by Thomas Lee on 1/31/2011 7:44:32 PM
This method doesn't support relative URI's (WebRequest.CreateHttp Method (String) (System.Net))
It's not explicitly stated in the documentation but supplying a relative URI to this method will throw a NotSupportedException which is pretty lame. WebClient can handle relative URIs, so you can use that, or you can construct an absolute URI from a relative URI by accessing the current pages URI. EG: Uri PageURI = System.Windows.Browser.HtmlPage.Document.DocumentUri;string URIWithoutPath = Pag
Last modified by Thomas Lee on 1/31/2011 7:44:05 PM
Elements containing dash (-) in name not supported by designer (The document contains errors that must be fixed)
There is a bug in Visual Studio designer. When you have a XML element in your code which contains dash in its name (e.g. <a-element/>) the designer breaks. To avoid this error either do not use elements with dashes in name (e.g. use <aElement/> instead) or if you can not store XML data in separate XML file. This is just designer bug, the code compiles and runs correct
Last modified by Thomas Lee on 1/30/2011 10:35:57 PM
Known bugs associated with this attribute (SectionInformation.InheritInChildApplications Property (System.Configuration))
You will have problems attempting to debug with this attribute in your main web.config. See this page for more information:https://connect.microsoft.com/VisualStudio/feedback/details/293526/web-debugging-fails-if-compilation-element-is-defined-inside-of-location-element You might also trigger a 502.22 error in IIS7 or above if you were previously relying on <validation validateIntegratedM
Last modified by Thomas Lee on 10/2/2010 11:52:27 AM
Tags:  productbug
Changing Me.Height and Me.Width in the OnLayout causes a conflict. (LayoutEventArgs.AffectedProperty Property (System.Windows.Forms))
If I understand what's happening, whenever you change Me.Width followed immediately by a change of Me.Height in a form's OnLayout, it causes the form's bounds to change, which schedules another call to the OnLayout event. Only, this appears to be an asynchronous call, because when you come back the second time, the Me.Width doesn't change. Mind, I'm only guessing about what's causing this, but it
Last modified by Thomas Lee on 9/26/2010 9:36:35 AM
Tags:  productbug
Page view tracker