Arrgh...
This lastest upate seems to want to break all sorts of existing code, have spent many hours fixing stuff that no longer works..
Reworking screens that break over bondaries and look like crap..
The lastest is causing vs 2008 to crash on startup is a real pain, forces vs restart, breaks VSS etc..
{"Telerik.Web.UI.VSX.AssemblyDiscovery.AssemblyLister needs to be initialized only once."}
" at Telerik.VSX.AssemblyDiscovery.AssemblyLister.Init()\r\n at Telerik.VSX.Helpers.UpdateChecker.VersionAvailabilityGetter_Complete(Object sender, EventArgs e)\r\n at Telerik.VSX.LatestVersionProcessing.BaseMonitoredProcess`1.DoAsyncJobAndRaiseCompleteEvent()\r\n at System.Threading.ThreadHelper.ThreadStart_Context(Object state)\r\n at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)\r\n at System.Threading.ThreadHelper.ThreadStart()"
This is a real pain...
Please do NOT make breaking changes and do some basic testing..
Saying we noted it in some file, does not fix my code..
Argh...
Ray..
5 Answers, 1 is accepted
0
Hi Ray,
I'm sorry for the frustration, the bug is a very nasty one indeed. We found it several days after the official release and we already fixed it.
Please, download the fix assembly, available in the Unhandled exception at "Telerik.VSX.AssemblyDiscovery.AssemblyLister.Init" forum post and follow the steps there to have the problem fixed.
Again, please excuse the frustration, this bug got unnoticed in our regression tests due to the specific conditions where an update check gets triggered.
By the way, I'm afraid I could not understand your point regarding "screens that break over bondaries and look like crap". Can you help us identify the screen you mention so that we can put a task to fix that?
Kind regards,
Erjan Gavalji
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
I'm sorry for the frustration, the bug is a very nasty one indeed. We found it several days after the official release and we already fixed it.
Please, download the fix assembly, available in the Unhandled exception at "Telerik.VSX.AssemblyDiscovery.AssemblyLister.Init" forum post and follow the steps there to have the problem fixed.
Again, please excuse the frustration, this bug got unnoticed in our regression tests due to the specific conditions where an update check gets triggered.
By the way, I'm afraid I could not understand your point regarding "screens that break over bondaries and look like crap". Can you help us identify the screen you mention so that we can put a task to fix that?
Kind regards,
Erjan Gavalji
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
0
Ray
Top achievements
Rank 1
Rank 1
answered on 19 Mar 2010, 11:03 PM
"We found it several days after the official release and we already fixed it."
I looked in the current intrim release area and there is nothing about this fix in the notes?
Craching vs is not a minor matter..
"By the way, I'm afraid I could not understand your point regarding "screens that break over bondaries and look like crap". Can you help us identify the screen you mention so that we can put a task to fix that?"
See my support tickets on this and all otehr issues, not resolved..
The response was to hack various solutions rather than actually fix the defect..
Bottom line this update has cost me a lot of time and effort, which could and should have been avoided with very basic QA...
I looked in the current intrim release area and there is nothing about this fix in the notes?
Craching vs is not a minor matter..
"By the way, I'm afraid I could not understand your point regarding "screens that break over bondaries and look like crap". Can you help us identify the screen you mention so that we can put a task to fix that?"
See my support tickets on this and all otehr issues, not resolved..
The response was to hack various solutions rather than actually fix the defect..
Bottom line this update has cost me a lot of time and effort, which could and should have been avoided with very basic QA...
0
Hi Ray,
You're right. We're planning an update which will address the VS crash, but it is still not available in the Latest Internal Builds page. Please, bear with us some more.
As per your inquiries regarding RadGrid, I'm sure my colleagues will help address them. I just want to make a note: Though we do our best to have the usage of our products as smooth as possible, sometimes it is not possible to rework a control to address a specific issue, as that would break other customers. For cases like that we do our best to provide as straightforward workarounds as possible.
Kind regards,
Erjan Gavalji
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
You're right. We're planning an update which will address the VS crash, but it is still not available in the Latest Internal Builds page. Please, bear with us some more.
As per your inquiries regarding RadGrid, I'm sure my colleagues will help address them. I just want to make a note: Though we do our best to have the usage of our products as smooth as possible, sometimes it is not possible to rework a control to address a specific issue, as that would break other customers. For cases like that we do our best to provide as straightforward workarounds as possible.
Kind regards,
Erjan Gavalji
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
0
Ray
Top achievements
Rank 1
Rank 1
answered on 22 Mar 2010, 11:07 PM
" Though we do our best to have the usage of our products as smooth as possible, sometimes it is not possible to rework a control to address a specific issue, as that would break other customers."
What the..
This is not a specifc issue... your controls breaks out of its container, the requirement is that your contol stays within Its container like all Msoft contolrs ajax or not..
This is one reason why nothing ever gets fixed, it is always the customers problem... same with the download bug etc, etc..
Please just concentrate on the problem, not the customer..
Its ironic that this break was caused, in my case by your chaneing the size of your filter icons, yes it broke the layout I was using, and now you are saying we dont want to fix the change as it would break the controls... ironic..
And you are correct the problem is a fundermatal design flaw, in that you dont have a container for the control, a very fundermatal aspect of all controls..
Mmm..
What the..
This is not a specifc issue... your controls breaks out of its container, the requirement is that your contol stays within Its container like all Msoft contolrs ajax or not..
This is one reason why nothing ever gets fixed, it is always the customers problem... same with the download bug etc, etc..
Please just concentrate on the problem, not the customer..
Its ironic that this break was caused, in my case by your chaneing the size of your filter icons, yes it broke the layout I was using, and now you are saying we dont want to fix the change as it would break the controls... ironic..
And you are correct the problem is a fundermatal design flaw, in that you dont have a container for the control, a very fundermatal aspect of all controls..
Mmm..
0
Hi Ray,
1. The appearance of the filter icons has changed, but the size has not - it was 22px / 22px before, as it is now.
2. If you want to ensure that the RadGrid content stays within the control's container, you should enable scrolling. Otherwise if the data cannot fit inside the specified width, it will overflow, which is normal. Surely the RadGrid control has a container, however, it does not have an overflow CSS style specified - you can add one like this:
<telerik:RadGrid style="overflow:auto" />
This is an alternative to using the control's built-in scrolling functionality.
Dimo
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
1. The appearance of the filter icons has changed, but the size has not - it was 22px / 22px before, as it is now.
2. If you want to ensure that the RadGrid content stays within the control's container, you should enable scrolling. Otherwise if the data cannot fit inside the specified width, it will overflow, which is normal. Surely the RadGrid control has a container, however, it does not have an overflow CSS style specified - you can add one like this:
<telerik:RadGrid style="overflow:auto" />
This is an alternative to using the control's built-in scrolling functionality.
Dimo
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.