Welcome Guest Search | Active Topics | Sign In | Register

Datepicker in Usercontrol -> Error Rendering Control . Specified method not supported Options
uwe
Posted: Monday, January 27, 2014 2:29:18 AM
Rank: Member
Groups: Member

Joined: 12/16/2007
Posts: 20
EO.Datepicker used in a Usercontrol.
The Usercontrol is not properly displayed in the containing Web Form in the VS ASPX Designer -> Error Rendering Control . An unhandled exception has occured. Specified method not supported

Problem occured after Upating from EO WEB 2012 to EO Total 2013 (EO.WEB 11.0.40.2)
Dev Env. VS2012 / VB.Net.
Thanks




uwe
Posted: Monday, January 27, 2014 9:28:55 AM
Rank: Member
Groups: Member

Joined: 12/16/2007
Posts: 20
Workaround: (pitty - works not allways)

After adding Culture=neutral
to the Register Assembly statement, the problem has gone for a while, but after a while the problem occured again.

<%@ Register Assembly="EO.Web, Culture=neutral" Namespace="EO.Web" TagPrefix="eo" %>
eo_support
Posted: Monday, January 27, 2014 11:21:33 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,196
Hi,

The root of the problem is a version mismatch on your machine. Most likely you have one version installed on your machine, but your project references a different version. So check the project reference and your web.config to make sure all referencing the same version as the one installed on your machine. After that rebuild your project and restart Visual Studio should fix the problem for you.

Thanks!
uwe
Posted: Monday, January 27, 2014 1:34:15 PM
Rank: Member
Groups: Member

Joined: 12/16/2007
Posts: 20
Hi .
How do I define the version in web.config
(Could not find the syntax in the EO Online Docu "Modifying Web.config" )

Currently I have
Under <httpHandler> and <modules> I use
<add name="EOWebRuntime" type="EO.Web.Runtime,EO.Web"/>

Thanks
eo_support
Posted: Monday, January 27, 2014 1:44:55 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,196
Hi,

If you have not referenced EO.Web in your web.config. Then you do not have to worry about that part. What our previous reply meant is, there can be multiple places in your project can keep EO.Web's version number. If they somehow kept a difference version number than the one that is installed, then you will run into version conflict issues. You can verify if that is the problem by creating a new blank test project and then see if you see the same problem in that project. If the problem only occurs with your project but not with the test project, then most likely its a version issue.

Thanks!
uwe
Posted: Monday, January 27, 2014 2:12:19 PM
Rank: Member
Groups: Member

Joined: 12/16/2007
Posts: 20
Hi,
in my Web Projects References there is not specific EO Version referenced, also not in my web.config.
Only "Choose Toolbox Items" shows the Version 11.0.40.2
The Problem started after updating from EO 12 to EO Total 13 on my main dev PC (Win7 64, VS 12).
On my Laptop (Win7 64, VS 12) the problem did not occur.
Thanks
eo_support
Posted: Monday, January 27, 2014 2:22:24 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,196
Hi,

You will want to search online about referencing DLLs in a project. We are not in a position to guide you through that. Your project won't even compile if your code uses our component but your project isn't referencing our DLL. So it's not possible that your project don't have a reference to EO.Web.

Thanks!
uwe
Posted: Monday, January 27, 2014 2:34:56 PM
Rank: Member
Groups: Member

Joined: 12/16/2007
Posts: 20
Hi,
I did not say there is no reference. My project of course references the EO DLL.
But the attribute "Specific Version" of the reference is "False".
Also my Web.config has a reference without Version Attribute (as mentioned).
I did not expect you to guide me through the basics :-). I am a SW developer since 30 yrs and use EO since many years.
I know about the difficulties of IT/SW support and try to write as precisely as possible.
As mentioned - the problem occured after upgrading to EO Total 2013 on one of two dev machines.

eo_support
Posted: Monday, January 27, 2014 2:50:52 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,196
Hi,

I apologize for the misunderstanding. In that case I would recommend you to try with a blank new project to see if that works and then go from there.

Thanks!
uwe
Posted: Monday, January 27, 2014 4:01:48 PM
Rank: Member
Groups: Member

Joined: 12/16/2007
Posts: 20
Thanks and no prb.
Unfortunately the solution consists of about 1500 source files and is based on Team Foundation Server.
In this case not easy to go from beginning. So I hoped we can isolate and fix the source of the problem.
(b.t.w. On the second dev. machine everything was fine after the EO update )
Uwe

eo_support
Posted: Monday, January 27, 2014 5:32:00 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,196
Hi,

We are not asking you to redo your project. The reason that we ask you to create a blank project is for you to compare a working project and a non-working project so that you might be able to find the difference. We would probably do the same if we were in the same position. There is nothing else we can tell you out of our head. We think it's a version issue, but we do not know where it could be.

Thanks!


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.