Blain Timberlake [mailto:[EMAIL PROTECTED]] wrote:
> One of our guys is attempting to use a server side treeview > control, and whatever he is attempting to do is apparently > NOT installed with the .Net redistributable framework we put > on that machine. Now it appears > it may be in the .Net SDK, but not in the .Net framework. The server side treeview control is 100% managed code and lives in the System.Web.UI which is installed as part of the basic .NET framework. Therefore, it should be available assuming the framework has been properly installed. > Alas, the > sysadmin doesn't think the SDK should be on a production server. Shouldn't need it and FWIW I agree with the admin's decision. > So what I have looked for, but cannot find, are some docs > about what needs to go where. What needs to be installed? > If we get a new server side control for asp.net is it > installed like an old school activex .ocx control is? That > has to be properly registered on the machine so you can give > it a clsid? If you're referring to third party components or controls, they would most likely be distributed with a strong name, be installed into any directory on the box (i.e. Program Files\Company Name) and then be registered in the GAC[1]. If you're paying for these controls then I'd hope the company is providing a setup program (i.e. MSI package) which should do all this for you. > I'm just a bit baffled here, and I can't find any Microsoft > document that basically says "If you want to make a .net > compatible server on windows 2000, do this." > > Is there anything like that? Can anyone help me out with > some info here? I grabbed a couple Asp.Net books for my own > reference, but nary to they mention the server setup at all. Sure, this[1] should get you started. HTH, Drew .NET MVP [1] http://msdn.microsoft.com/library/en-us/cpguide/html/cpconworkingwithassembl iesglobalassemblycache.asp?frame=true [2] http://msdn.microsoft.com/downloads/sample.asp?url=/msdn-files/027/000/976/m sdncompositedoc.xml&frame=true You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.