Eve Cunning
Top achievements
Rank 1
Rank 1
Eve Cunning
asked on 12 Jan 2007, 07:03 PM
As a web developer, I have been thrilled to look through all the wonderful features of Microsoft's shiny new IDE, Web Expression.
However, it's SO new, it doesn't look like it supports third-party controls very well at all (yet). It doesn't seem to accept our custom C#/ASP.NET controls we've developed in house, nor does it want to import telerik's.
Are you all currently working through that issue? We could find ways to go forward without our controls in order to use Expression, but we really would be stuck without telerik's!
--Eve
However, it's SO new, it doesn't look like it supports third-party controls very well at all (yet). It doesn't seem to accept our custom C#/ASP.NET controls we've developed in house, nor does it want to import telerik's.
Are you all currently working through that issue? We could find ways to go forward without our controls in order to use Expression, but we really would be stuck without telerik's!
--Eve
3 Answers, 1 is accepted
0
Hello Eve,
Thank you for the feedback.
We do not currently support Expression Web as a development tool since it still has some limitations when dealing with custom controls. We are testing the controls in this new environment and trying to find out some workarounds for the major obstacles (toolbox registration, intellisense, property grid, design-time preview)
There are quite a few articles and forum/blog posts which describe most of the workarounds/limitations. Expression Web Program Manager's blog is a good read:
http://blogs.msdn.com/andrewj/archive/2006/12/13/custom-asp-net-controls-and-expression-web.aspx
We will be very happy to hear feedback from the community:
Have you tried using any custom controls with Expression Web?
What are the major challenges you face with this new environment?
Greetings,
Ivo
the telerik team
Thank you for the feedback.
We do not currently support Expression Web as a development tool since it still has some limitations when dealing with custom controls. We are testing the controls in this new environment and trying to find out some workarounds for the major obstacles (toolbox registration, intellisense, property grid, design-time preview)
There are quite a few articles and forum/blog posts which describe most of the workarounds/limitations. Expression Web Program Manager's blog is a good read:
http://blogs.msdn.com/andrewj/archive/2006/12/13/custom-asp-net-controls-and-expression-web.aspx
We will be very happy to hear feedback from the community:
Have you tried using any custom controls with Expression Web?
What are the major challenges you face with this new environment?
Greetings,
Ivo
the telerik team
0
Eve Cunning
Top achievements
Rank 1
Rank 1
answered on 19 Jan 2007, 04:42 PM
Thanks for your response, Ivo. I am sure that if it is at all possible, the telerik team will work out the kinks with importing to Expression.
My hope was that it was an easy process, LOL, and updates were soon to follow (and you all might have some good pointers on how to accomplish importing).
However, my assumption was that no, it's not so simple, and we are all having to jump the same strange hurdles.
I am going to try what Andrew outlines in his blog when I get an opportunity.
Thanks again,
Eve
My hope was that it was an easy process, LOL, and updates were soon to follow (and you all might have some good pointers on how to accomplish importing).
However, my assumption was that no, it's not so simple, and we are all having to jump the same strange hurdles.
I am going to try what Andrew outlines in his blog when I get an opportunity.
Thanks again,
Eve
0
Josef Rogovsky
Top achievements
Rank 2
Rank 2
answered on 22 Mar 2007, 07:56 PM
I read somewhere recently that Microsoft changed their mind about the Expression Suite and that it will be targetted exclusively to designers now (developers are no longer a focus) and that the nifty design features in the Expression Suite will be integrated into the next version of Visual Studio.
My guess is that there is going to be poor support in the Expression Suite for many of these developer centric requirements (like third party controls) for a while yet.
My guess is that there is going to be poor support in the Expression Suite for many of these developer centric requirements (like third party controls) for a while yet.