Assisted Solutions Forums

I changed it back to

<%@ Import Namespace="AssistedSolutions.WebControls.CityStateFinder" %>

It looks like its finding the dll now but I am getting a different error

BC30456: 'SearchOn' is not a member of 'CityStateFinder'.

and here is the source I am using in my aspx page

<%@ Import Namespace="System.Web.UI" %>
<%@ Import Namespace="AssistedSolutions.WebControls.CityStateFinder" %>
<script language="VB" runat="server">
Sub Page_Load(Src As Object, E As EventArgs)
 Dim i as integer
          Dim locations() as CityStateLocations
          locations = CityStateFinder.SearchOn("28412")
          For i = 0 To locations.length - 1
              response.write(locations(i).StateName)
          Next         
end sub
</script>

I looked into this earlier this morning, and then again a few minutes when I had a few minutes.  I cannot replicate this in VS.NET and I don't have access to a Dreamweaver install.  That error would seem to imply that Dreamweaver isn't parsing the control properly to find the SearchOn function.  As you type in the code window, does Dreamweaver show you the class properties, methods and functions?  If so, type "AssistedSolutions.WebControls" onto the page and see what the code window suggests as to the nested class members that are available.

I wish I could help more on this.  The control is so easy and simple to use, it is frustrating that I can't reproduce this problem for you.  I'm almost inclined to install Dreamweaver...

dreamweaver doesn't work like VS the file I am using is just a simple .aspx file with the code that in it. And I have all of the dlls placed in a bin folder in the root of the site.
Maybe could you email me a working file that works for you because it feels like a simple syntax error?

When you paste the above code into an aspx file and run it does it work?

Yes it does work for me, hence the confusion.  Notice the screenshots below.  The first shows the code in Visual Studio and the second shows the output when the app is run in IE.  I have also attached the test project I created.  Run this app your end and tell me what you get.

The code in Visual Studio 2003:



The output when the project is run in IE:

ok it must be something in your web.config file or global file because when I take the ziped file you attached and upload it to a directory I get all kinds of web config errors if I delete the web.config and global asax files then I get the error that I was posting before

so I tried putting the web.config and global.asax files back and find out what I need to do to get past these errors
the first one I thought would be easy
it was in the web.config file

<authentication mode="Windows" />

well since I am testing this remotely on my webserver I changed that to "None"  but now I am getting this error

Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.

Source Error:

Line 37: by Microsoft that offers a single logon and core profile services for member sites. Line 38: --> Line 39: <authentication mode="None" /> Line 40: Line 41:

\testing\newcity\web.config    Line: 39

That error has nothing to do with the authentication mode.  You can leave that as Windows or None.  That errors means you don't have a valid virtual folder setup in IIS.  You cannot run a web application in asp.net 1.1 without a virtual folder setup in IIS.  Have you done this before? 

Leave all the content I sent as it was, and go into IIS and bring up the properites for the application where it resides.  If you place the application under c:\inetpub\wwwroot\ then it should be showing in IIS under the Default Web Site node (this is the default location).  After you bring up the properties of the root folder, click the Create Application button so that IIS knows that it is serving a valid web application and parses the web.config file accordingly.  Other tweaks may also be necessary.

oh man you know its always something easy

I replaced the dll I was using with the one in that zip file and it worked
it must have gotten corrupt somewhere along the lines