• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2173
  • Last Modified:

Error creating control - Scriptmanager1

I have just installed VS2008. I then got the 3.5 SP1 update installed. Then I installed the AJAX 3.5 Toolkit. I then go into VS, select File/New AJAX Control Toolkit Web Site (VB) and as expected, the Scriptmanager1 is installed by default in the default.aspx code page. When I switch to Design View, VS can not display the Scriptmanager and shows the error: Error creating control - Scriptmanager1. Unable to create type...blah, blah.
I can at this point, delete the Scriptmanager, go into my AJAX Toolbox on the Tools panel and drag a Scriptmanager onto the form. When I do, I get a popup that reads: Destination File Exists - A file with the name 'Bin/AjaxControlToolkit.dll' already exists. Do you want to replace - for each control that I drop on the form? If I say yes to all, all is well and I can continue to code.
My question is, why is all of this happening? The default Scriptmanager on the page should work, and I shouldn't be prompted about existing files.
What, where, and how do I fix this problem?
Thanks,
Eric
0
phc_dev
Asked:
phc_dev
  • 2
  • 2
2 Solutions
 
NerdsOfTechTechnology ScientistCommented:
http://forums.asp.net/p/1268079/2388841.aspx#2388841

OR Try

' source/library/components/framework/Ajax.vb
 
' Line #148
        Public Shared Sub RegisterScriptManager()
            If Not IsEnabled() Then
                AddScriptManager(m_Page)
            End If
        End Sub
 
'ADDED THE FOLLOWING FOR THE FIX
        Public Shared Sub RegisterScriptManager(ByVal objPage As Page)
            If Not IsEnabled() Then
                AddScriptManager(objPage)
            End If
        End Sub

Open in new window

0
 
NerdsOfTechTechnology ScientistCommented:

        Public Shared Sub RegisterScriptManager(ByVal objPage As Page)
            If Not IsEnabled() Then
                AddScriptManager(objPage)
            End If
        End Sub

Open in new window

0
 
phc_devAuthor Commented:
Couple of questions?

Is this a known bug?

Where is this path located:
' source/library/components/framework/Ajax.vb

once I put that code in place, will i have to also make sure our servers are setup that way too?

also, after I put that code in place, will it correct the second part of my question:
"I can at this point, delete the Scriptmanager, go into my AJAX Toolbox on the Tools panel and drag a Scriptmanager onto the form. When I do, I get a popup that reads: Destination File Exists - A file with the name 'Bin/AjaxControlToolkit.dll' already exists. Do you want to replace - for each control that I drop on the form? If I say yes to all, all is well and I can continue to code."

Thanks.
0
 
phc_devAuthor Commented:
The above fix is for dotnetnuke which I do not have. I have read several articles since my original posting which say that 2008 + ajax 3.5 = flakey at best and to stick to the older version, which I am reverting to.
Eric
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now