Hy,
we had 2 projects where we had older Telerik controls in use. Now we installed the new Telerik Controls for Windows Forms and have major problems with this.
Some smaler problems was that some black writing on white background was now white on thite background.
But the bigest Problem ist that ist nearly impossible so get into the Form.cs[Design]. Only if you get the latest Version 2 to 3 times you can work with the Design for about 1 hour.
The arror message ist
I hope someone can help me.
we had 2 projects where we had older Telerik controls in use. Now we installed the new Telerik Controls for Windows Forms and have major problems with this.
Some smaler problems was that some black writing on white background was now white on thite background.
But the bigest Problem ist that ist nearly impossible so get into the Form.cs[Design]. Only if you get the latest Version 2 to 3 times you can work with the Design for about 1 hour.
The arror message ist
| One or more errors encountered while loading the designer. The errors are listed below. Some errors can be fixed by rebuilding your project, while others may require code changes. | |
|
at System.IO.Path.NormalizePathFast(String path, Boolean fullCheck) at System.IO.Path.GetFullPathInternal(String path) at System.Reflection.AssemblyName.GetAssemblyName(String assemblyFile) at Microsoft.VisualStudio.Design.VSTypeResolutionService.AddProjectDependencies(Project project) at Microsoft.VisualStudio.Design.VSTypeResolutionService.AssemblyEntry.get_Assembly() at Microsoft.VisualStudio.Design.VSTypeResolutionService.AssemblyEntry.Search(String fullName, String typeName, Boolean ignoreTypeCase, Assembly& assembly, String description) at Microsoft.VisualStudio.Design.VSTypeResolutionService.SearchProjectEntries(AssemblyName assemblyName, String typeName, Boolean ignoreTypeCase, Assembly& assembly) at Microsoft.VisualStudio.Design.VSTypeResolutionService.SearchEntries(AssemblyName assemblyName, String typeName, Boolean ignoreCase, Assembly& assembly, ReferenceType refType) at Microsoft.VisualStudio.Design.VSTypeResolutionService.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase, ReferenceType refType) at Microsoft.VisualStudio.Design.Serialization.CodeDom.AggregateTypeResolutionService.GetType(String name, Boolean throwOnError, Boolean ignoreCase) at Microsoft.VisualStudio.Design.Serialization.CodeDom.AggregateTypeResolutionService.GetType(String name, Boolean throwOnError) at System.ComponentModel.Design.Serialization.CodeDomSerializerBase.GetType(ITypeResolutionService trs, String name, Dictionary`2 names) at System.ComponentModel.Design.Serialization.CodeDomSerializerBase.FillStatementTable(IDesignerSerializationManager manager, IDictionary table, Dictionary`2 names, CodeStatementCollection statements, String className) at System.ComponentModel.Design.Serialization.TypeCodeDomSerializer.Deserialize(IDesignerSerializationManager manager, CodeTypeDeclaration declaration) at System.ComponentModel.Design.Serialization.CodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager manager) at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager serializationManager) at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.DeferredLoadHandler.Microsoft.VisualStudio.TextManager.Interop.IVsTextBufferDataEvents.OnLoadCompleted(Int32 fReload) |
|
I hope someone can help me.
1 Answer, 1 is accepted
0
Hello David,
Thank you for contacting us with this problem.
We are not sure that this VS2005 error is related to our controls, although it certainly seems so. In an effort to locate what may be causing it, we did a quick Google search and found several links which should help you fix the error. I will suggest researching the problem in depth, because many people are having the same problem and the solutions vary.
In most cases it seems that the problem is that the form's designer is trying to locate one of the types referenced by your form, but is unable to do so. This means that your project probably wasn't built since the reference was added or that the project file has somehow been changed. If building the solution doesn't work, try going over the references in the project and looking at where their locations are and verifying that they all actually exist.
I will also suggest reviewing the following Microsoft Connect case: Feedback: "The path is not of a legal form." (click on VIEW WORKAROUNDS at the top to view possible solutions).
Here is yet another Forum with possible resolutions:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=515657&SiteID=1
We will be happy to know how you managed to fix the error.
Best wishes,
Vassil
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Thank you for contacting us with this problem.
We are not sure that this VS2005 error is related to our controls, although it certainly seems so. In an effort to locate what may be causing it, we did a quick Google search and found several links which should help you fix the error. I will suggest researching the problem in depth, because many people are having the same problem and the solutions vary.
In most cases it seems that the problem is that the form's designer is trying to locate one of the types referenced by your form, but is unable to do so. This means that your project probably wasn't built since the reference was added or that the project file has somehow been changed. If building the solution doesn't work, try going over the references in the project and looking at where their locations are and verifying that they all actually exist.
I will also suggest reviewing the following Microsoft Connect case: Feedback: "The path is not of a legal form." (click on VIEW WORKAROUNDS at the top to view possible solutions).
Here is yet another Forum with possible resolutions:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=515657&SiteID=1
We will be happy to know how you managed to fix the error.
Best wishes,
Vassil
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center