Speechlib上共享主机 - ASP.NET [英] Speechlib on Shared hosting - ASP.NET

问题描述

我想使用SpeechLib在我的个人网站。这是一个非常简单的应用程序，节省了一些文字为WAV文件 - 标准的东西。在开发计算机上的伟大工程。但是，所有的地狱破散时，我把它部署到共享的主机。

有时我在写的wav文件时提示输入用户名和密码。有时候，我得到的安全例外。该网站有充分的信任，我可以写从我的应用程序，一个简单的txt文件，没有任何问题。

在冲刷互联网，我意识到SpeechLib组件暂时写到一个文件：

  C：\用户\ XX \应用程序数据\漫游\微软\语音\文件\ UserLexicons
 

我验证这个开发机上。它确实做。

所以，我的猜测是，共享主机，ASPNET没有权限写入该文件夹（？）。所以，我contaced托管服务只被告知我必须升级到虚拟专用服务器。我不知道，如果他们知道他们在说什么。

有没有人得到SpeechLib工作共享的主机上。下面是我面临完全一样的问题：

http://www.eukhost.com/forums/f41 /互操作-speechlib-DLL-6743 /

有什么想法？

解决方案

我不知道该产品，但我会寻找（或与他们联系）的方式将其配置为使用不同的临时目录。你会更容易得到你想要的东西比puruing托管公司。

我完全理解为什么他们会要你不过升级，（而且它不只是更多的钱）。

在C：Users \用户XX在这种情况下，目录将可能是大家在共享主机相同的目录，因为它会在目录中的任何帐户Asp.Net下运行，而不是每个用户谁在登录<。 / P>

在一个专用的服务器或vitual私人服务器，你会是唯一一个在该环境中运行，所以你可以有机会获得一个用户目录（仍然不是一个好主意，这样做）。

不知道这是否会帮助或没有，但它是我将如何对待它。

I am trying to use SpeechLib on my personal website. It's a very simple app that saves some text to a wav file - standard stuff. Works great on the dev machine. But all hell breaks loose when I deploy it to the shared host.

Sometimes I get prompted for user name and password at the time of writing the wav file. Sometimes, I get the "Security exception". The site has full trust and I can write a simple txt file from my app without any issues.

On scouring the internet, I realized that the SpeechLib component temporarily writes a file to:

C:\Users\XX\AppData\Roaming\Microsoft\Speech\Files\UserLexicons

I verified this on the dev machine. It indeed does.

So, my guess was that on the shared host, ASPNET does not have rights to write to that folder(?). So, I contaced the hosting service only to be told I have to upgrade to Virtual Private Server. I am not sure if they know what they are talking about.

Has anyone gotten SpeechLib to work on the shared host. Here's the exact same issue I am facing:

http://www.eukhost.com/forums/f41/interop-speechlib-dll-6743/

Any thoughts?

解决方案

I don't know that product, but I would search for (or contact them about) a way to configure it to use a different temp directory. You will be more likely to get what you want than by puruing the hosting company.

I completely understand why they would want you to upgrade, however (and it isn't JUST for more money).

The C:Users\XX directory in this case would likely be the same directory for everyone in the shared hosting, since it would be the directory for whatever account Asp.Net is running under, not per user who logs in.

In a private server or vitual private server you would be the only one running in that environment, so you could have access to a user directory (still not a great idea to do it).

Don't know if this will help or not, but it's how I would approach it.

这篇关于Speechlib上共享主机 - ASP.NET的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！