I m using VS2010. I wrote code that speaks by taking input from text box when I click on button.but the button works fine when I run it on system but not work on IIS. TTS engine is not working on IIS server and I'm not getting any voice.
At a guess, your TTS code is running in the code-behind. That code runs on the server, not the client.
It appears to work when you run the site from Visual Studio, but that's only because the server and the client are the same machine in that specific scenario.
When you deploy it to a real server, the code will either fail, or it will make the server speak. Whilst that might be a good trick to scare your IT staff, the user isn't going to hear it.
There is an unofficial client-side speech API, but browser support is extremely limited. Unless all of your users are using Chrome, Safari or Opera, then it's not going to work.
Related
First off, I'm not a web developer, so I might be asking the question in the wrong place. Unfortunately, I've tried searching regarding my problem but most of the issues I see are web-developer server side issues, so I'm runnig out of places to turn.
The problem: I'm trying to navigate a website, and eventually it decides to try running a ".asp" page. However, my browser just hangs (attempted Firefox and IE11), until it eventually times out. However, when I've run the same website on other machines (such as my phone), those pages load flawlessly. The fact that it's browser independent seems to suggest it's something with my local machine (Win7). I've ensured the IIS feature is turned on and the process is running, but still nothing.
The only other evidence I have is while searching for ASP tutorials, there was an example designed to show the current date/time which didn't work. The rest of the page which was straight HTML was then fine. I'm not sure if it's possible that some native binary for a scripting language isn't loading, but I'm not sure how I can debug that.
To summarise, my questions are as follows:
What could stop an ASP page being loaded on a client machine?
What can I do to ensure the right dependencies are present on a client machine such that it can load ASP pages?
To note, I'm not aware of anything I've installed which would affect this. The only code related program on my PC is Visual C++ Express 2013, but I'm not sure what that would do. .Net 4.5 is installed but I don't know how to tell what script the asp page is attempting to execute.
* What could stop an ASP page being loaded on a client machine?
IIS?
IIS is the one responsible for parsing asp code.
IIS takes your ASP code, and then, transforms it into html code, then sends it to the client.
There might be an issue with your windows 7 computer, but there is nothing related to ASP.
* What can I do to ensure the right dependencies are present on a client machine such that it can load ASP pages?
There are no such dependencies. Your client makes a call to a server, which returns html code.
I have made some changes to a view in my ASP.NET MVC3 application, but the changes I have made are not showing up when I test/debug the site within the browser. The changes I am making are simple text amendments to the markup.
I am using the Visual Studio development server for testing the application.
The odd thing is, I have tried publishing these changes to IIS and the changes I have made to the view are working when I test the application using the IIS server.
It is only when testing in the Visual Studio environment that this seems to happen.
Thanks,
A common problem i've run into is when you are not using IE and you close the debug session, but not your browser.
This means that the "IIS/development server" is still running in your system tray, but it is running on the old compiled code, if you hit ctrl + shift + b, you build your entire solution and re-publish your code to your development server. this allows you to hit refresh (F5) in your browser and the changes you've made to the razor view should now be reflected in your browser.
Are you using IE? Maybe deleting the cache or using another browser should work? I've had a lot of problems with that :D
Solution is to use IIS Express. For some reason, the VS development server doesn't recognise changes to code behind - nothing to do with caching on the browser.
However the location of the source code as suggested in other answers is important - it works for me using the c:\windows folder or c:\users\DefaultAppPool - apparently it has something to do with security to ensure.
Only applications running under the 'DefaultAppPool' identity are permitted under IIS. So, for anyone using a VM and mapping the host OS code folder you won't be able to rectify this unless you copy to a local folder in the c:\users\DefaultAppPool folder.
You may also now have difficulties accessing the SQL server database established for the Membership Provider under ASP.NET. For more details on how to fix that, I've posted on my blog.
Basically we have this aspx script generated by another company, which we need to run, we normally just use coldfusion, for our company.
However this app is an aspx.
We have both a development and production server, it works flawlessly on our dev server, but it fails to work at all in the production server.
It uses a javascript function called _doPostBack.
I have compared the aspx files on dev/prod line by line, and they are 100% identical.
So I need some ideas what iis7 setting to change to allow this to work. Since we didn't do anything special to make it work on our development server.
Our Prodution server is sql2008, iis7, win 2008 i believe.
Our Development server is sql 2005 express, iis7, vista business edition.
Any suggestions or tips we can do?
And in firebug it generates no javascript errors of any code, but the navigation links do nothing.
The page itself displays, on the left is a list of links, which if clicked on, should change the content on the right/main content area.
This works fine on dev, it doesn't work at all on production. It does display the page, show's no javascript errors, but the navigation links do not work.
There is no external javascript file, so it must be something in iis.
Thanks
I would consider reinstalling asp.net on the box that isn't working. Can be done from command line using aspnet_regiis -i
http://msdn.microsoft.com/en-us/library/k6h9cz8h.aspx
Other than that I have no idea. Sounds like a config issue to me though..
In the IIS settings, make sure the ASP.NET System Services is running and verify that ASP.NET exists in the Role Services. Also check the Application Pools and in the Advanced Settings, you can check the .Net framework version.
What happens if you try to acccess a page you create called test.aspx with plain text?
You can try running the page locally on the production server, sometimes things will work locally but not remotely if it's an IIS issue.
Have you verified that the appropriate .Net framework is installed on the machine and that the page resides in an application in IIS?
Using IE8, press F12 to bring up the developer tools. Inside the tools you can examine the various scripts that are (or will be) running, and start debugging. Start the debugger and set a breakpoint where the _doPostBack function is being called (or inside the function itself) and see what is actually happening.
Also, you may want to fire up Fiddler2 and compare the HTTP requests between your development and production servers. It is entirely possible that something else isn't returning as expected (like a call to WebResource.axd) in production that works fine in dev.
We have this nice Silverlight 3 application that communicates with a web server running some WCF web services. It works well when it is running in the browser, but at soon we try to run it outside the browser it doesn't call our webservices.
I have tried to find out why this is happening, but I can't find any explanation.
When attaching the debugger to the sllauncher.exe process I am able to step through the code and I can see that the (Begin)Async method is called. But using Fiddler I can see that there is no traffic to the server at all!
I have also verified that the endpoint address is correct and that the endpoint is properly configured (it works when running in the browser after all).
So I am wondering what can be the cause of the problem and how to debug it. Any ideas?
EDIT:
I noticed that our application doesn't run in Internet Explorer either. But it runs fine in Firefox! This isn't much of a surprise since the out of browser application embeds internet explorer, but it may be a clue to our problem.
So, do you know of any differences between hosting silverlight in Firefox versus Internet Explorer?
Maybe worth putting a try catch around your web service call and see what exception is thrown to help further debug this issue as webservices that work ok in browser should work OOB as far as I'm aware.
The issues we have experiences with OOB have all had to do with local machine setup. If you are behind a proxy, turn it of temporarily. Also check your firewall to ensure it will let the web service traffic through.
For easier debugging, if you have not already done so, wrap your service calls like this:
using System.Net;
if (NetworkInterface.GetIsNetworkAvailable()) { doSomethingAsync(); }
else { //Report the error or show status in UI }
It works in Firefox and not IE, because firefox is alot more willing to accept temporary certificates. Are you running a certification server?
The reason no traffic hits fiddler is because either
You have no clientaccesspolicy.xml on the HTTPS address you are accessing.
you are running the Silverlight app from within visual studio, hence running the website that hosts the SL clientbin from within visual studio, the ASP development server prevents certain calls from being made, esp if your webservice address is different from the address that the website is hosted on and certain ports dont respond resulting in the most odd behavior of fiddler doing absolutely nothing.
Either way the behavior of the SL app not contacting the web server when using HTTPS, is due to the hosting environment restrictions (try deploying in IIS) or the willingness of the client to accept the certification encryption strategy.
This is strange and baffling. In my ASP.NET 2.0 app I have a form that uses a number of client-side validators. Custom, Regularexpression and RequiredField. My app requires that I enable or disable certain validators based on a dropdown selection. I do this in my codebehind event. All this works great in my dev environment however when I deploy to the server it does not. Mainly when I run the app from the server it will not allow me to enable or disable the validators in code. When I set the enabled property in the aspx file it remains in that state regardless of what I do in the server event. Again - this works perfectly in dev. Any suggestions? Could it be the version of .NET 2.0 is different on my dev machine and the server? I am at a loss and we are heading for production soon. Please help!
This turned out to be a .NET version issue. Once I applied the 2.0 Service Pack 2 on the server my problems went away.
Do the validators work at all on the production machine? That is, do they prevent you from entering invalid data?
I have a vague recollection of something like this happening to me. It may have been an issue of the JavaScript file needed by the validators not being sent from the server. Do a View Source, or turn on debugging (FireBug or IE8's F12 command). See if you're maybe getting JavaScript errors you didn't know about.