You searched for the word(s): userid:35641

More Search Options

RSS Available

• Re: Protecting non-ASP.NET Office 2007 files mangles content

  Hi Tom, Thank you for getting to the bottom of this issue! You're right. Unfortunately ASP.NET does maintain a hard-coded list for MIME type mappings in StaticFileHandler. Unrecognized extensions are mapped to "application/octet-stream". We will fix this issue for all well-known extensions in our next release. For released ones, your work-around is a great solution. (Another place such work-around can be implemented will be global.asax, for example in event Application_PostRequestHandlerExecute

  Posted to Security (Forum) by qingye on 6/29/2009

• Re: Python is not a supported language

  You likely don't have the right bits installed. - do all assemblies exist under bin of your web app? Microsoft.Web.Scripting.dll Microsoft.Scripting.dll IronPython.dll IronPython.Modules.dll - does web.config have the needed settings? <pages compilationMode="Auto" pageParserFilterType="Microsoft.Web.Scripting.UI.NoCompileCodePageParserFilter"> </pages> <httpHandlers> <add path="*.py" verb="*" type="System.Web.HttpForbiddenHandler"

  Posted to IronPython for ASP.NET (Forum) by qingye on 12/5/2007

• Re: Python is not a supported language

  It is IronPython that is supported.

  Posted to IronPython for ASP.NET (Forum) by qingye on 12/4/2007

• Re: Python 3000 alpha 1 - For .NET

  Hi, Current IronPython release is compatible with Python 2.4. We will add new features, including features in Python 3000, in a future release. For more information please visit http://www.codeplex.com/IronPython . Thanks, Qing

  Posted to IronPython for ASP.NET (Forum) by qingye on 9/4/2007

• Re: What Is The Use Of Personal Web Site Starter Kit?

  It is only a sample. There are C# and VB version of Personal Web Site Starter Kit as well. Thanks, Qing

  Posted to Personal Site Starter Kit (Forum) by qingye on 8/3/2007

• Re: Error when uninstalling IronPython for ASP.NET CTP

  Hi MetalJon, "IronPython for ASP.NET CTP" cannot be uninstalled when VS is running and the corresponding package is loaded. However, it's a bit unusual that instead of a setup failure, VS crashed! Anyway, in order to have ASP.NET Futures CTP installed, there is a registry hack you could try. Remove below key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\Packages\{c028a7f9-dfa1-41e8-b834-f96eb092480a} hope it helps! Qing

  Posted to IronPython for ASP.NET (Forum) by qingye on 7/26/2007

• Re: Working Examples in IronRuby...?

  Hi, I assume you are asking about IronRuby in ASP.NET, since this is an ASP.NET forum. We're currently still working on solving some key issues in order to enable IronRuby. We don't have a concrete date yet. But John will blog it for sure once we have a plan. Thanks, Qing

  Posted to ASP.NET Futures (Forum) by qingye on 7/23/2007

• Re: how to determine what database to use??

  Below section in blod is what David referred to, it should be placed before any other sections. <configuration> <configSections> <section name="dynamicDataControls" type="Microsoft.Web.DynamicDataControls.DynamicDataControlsSection"/> </configSections> <dynamicDataControls showAllTables="true" /> ... </configuration> Thanks, Qing

  Posted to ASP.NET Futures (Forum) by qingye on 7/18/2007

• Re: Problems with Futures (May) install and .NET Hotfix

  ... and you've also saved the msi file locally on your machine? (just in case it's on a share somewhere that you account doesn't have access.) If so, you may try Windows Installer Cleanup Utility which is called as a solution for this error on many web sites. Personally, I wouldn't recommend this tool as I never tried it before. I think a safer choice is to get .netFramework 3.5 beta1 installed. Once that is done, this 2.0 hotfix is no longer required by ASP.NET Futures CTP. Thanks

  Posted to ASP.NET Futures (Forum) by qingye on 6/19/2007

• Re: Problems with Futures (May) install and .NET Hotfix

  Hi, This could be due to insufficient privilege of current logon user. logon as admin and run ASPNETFutures.msi locally might help. Alternatively, if you could have .net framework 3.5 beta1 installed, this patch will no longer be required. The 3.5 beta1 could be downloaded from http://www.microsoft.com/downloads/details.aspx?FamilyId=E3715E6F-E123-428B-8A0F-028AFB9E0322&displaylang=en . Thanks, Qing

  Posted to ASP.NET Futures (Forum) by qingye on 6/18/2007