My Visual Studio gives me a warning that the properties Behaviour, InitialBehaviour and ClientCallBackFunction properties are obsolete...
For ClientCallBackFunction, it suggests using OnClientClose instead
Yet, the documentation does not mention any of them as obsolete...
Is something not quite right???
Thanks
Eric
For ClientCallBackFunction, it suggests using OnClientClose instead
Yet, the documentation does not mention any of them as obsolete...
Is something not quite right???
Thanks
Eric
4 Answers, 1 is accepted
0
Eric
Top achievements
Rank 1
answered on 16 Apr 2009, 08:56 AM
If anyone is interested, I just assumed the documentation in 2009 Q1 is out of date and that the warnings are correct.
Therefore I have removed Behaviour, InitialBehaviour and ClientCallBackFunction (I use OnClientClose instead).
It looks like the RadWindowManager was doing a complete mess of my page at design time (not able to view the page in design or split mode) and everything went back in order when I moved my RadWindow page(s) outside of the RadWindowManager.
I only use RadWindowManager on its own to enable the use of RadAlert(), RadPrompt() etc...
Looks a bit flaky to me all this...
Therefore I have removed Behaviour, InitialBehaviour and ClientCallBackFunction (I use OnClientClose instead).
It looks like the RadWindowManager was doing a complete mess of my page at design time (not able to view the page in design or split mode) and everything went back in order when I moved my RadWindow page(s) outside of the RadWindowManager.
I only use RadWindowManager on its own to enable the use of RadAlert(), RadPrompt() etc...
Looks a bit flaky to me all this...
0
Hi Eric,
Indeed, the Behavior and the InitialBehavior properties are marked as obsolete for the last several months. This however, is noted in the Changes and Backward Compatibility section of the documentation since we made that change.
As for the problem with VS design time, could you please provide some more information on what exactly is the problem? What were the actions that you took and what was the result?
Kind regards,
Georgi Tunev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Indeed, the Behavior and the InitialBehavior properties are marked as obsolete for the last several months. This however, is noted in the Changes and Backward Compatibility section of the documentation since we made that change.
As for the problem with VS design time, could you please provide some more information on what exactly is the problem? What were the actions that you took and what was the result?
Kind regards,
Georgi Tunev
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Eric
Top achievements
Rank 1
answered on 16 Apr 2009, 04:24 PM
Unfortunately, I am not able to supply simple information because it does seem to come and go as it pleases...
The page I use most is also quite complex with Master page containing several ContentHolder.
The common thread to the problems seems to be that it complains about trying to cast an object to an object of the same class but from a different DLL in temporary folders in Document and Settings / ... / Local Settings / ... / ProjectAssemblies / ...
Is there any way to send you a screen shot?
Eric
0
Eric
Top achievements
Rank 1
answered on 16 Apr 2009, 04:38 PM
Actually,
I just managed to fix it (again) by deleting all data in the folder
C:\Documents and Settings\eric.mamet\Local Settings\Application Data\Microsoft\VisualStudio\9.0\ProjectAssemblies
(after stopping Visual Studio...)
It would be nice if I could avoid this happening too often...
Eric
I just managed to fix it (again) by deleting all data in the folder
C:\Documents and Settings\eric.mamet\Local Settings\Application Data\Microsoft\VisualStudio\9.0\ProjectAssemblies
(after stopping Visual Studio...)
It would be nice if I could avoid this happening too often...
Eric