I'm writing a Silverlight application in Visual Studio 2010 leaning on the walktroughs in the Lync SDK.
If I run the application in VS 2010 it all works in debug and in the release version.
If I try to deploy this to IIS7 the Silverlight is also running but I can't see the presence. The little square is without a filling color.
I assume some configuration is missing on IIS7?
My environment is a Windows Vista PC with local IIS7.
Can someone help me?
Did you add the site to your browsers Trusted Sites zone? see the answer here
This is a bug in Lync SDK
http://support.microsoft.com/kb/2464845
The combination of adding the site to the Trusted Sites zone in addition to installing the fix below seems to resolve this issue.
Cumulative update package for Lync 2010: January 2011
Related
Tried everything. Deploying same type of web project (Net.Core 1.1) with VS2015 at the very same location using exactly same parameters works without any problems.
Is there any known issue with release RC.4+26206?
This what my server log says:
IISWMSVC_AUTHORIZATION_SERVER_NOT_ALLOWED
Only Windows Administrators are allowed to connect using a server connection. Other users should use the 'Connect To Site or Application' task to be able to connect.
Process:WMSvc
User=sludr
Ok... Found a solution. Same reason as documented here: .net core web deploy requires admin permissions, so VS2017 requires right now a windows account of group Administrators to publish net core projects.
Hopefully this will be fixed soon.
Note: The official VS 2017 RTW still has this bug.
I am attempting to deploy a simple lightswitch application (HTML not Windows app) in VS 2013. I have selected to not have authentication to make the testing easier.
The IIS server and the database server are on different machines. I have followed the steps here for server setup.
However, when I go to the website after publishing, I get this error:
You do not have permission to view this directory or page.
I went to the IIS server and made sure that only Windows authentication was enabled on the application that was sent over. After reading another MS article on the 401 error, they recommended unchecking the Kernel Mode Authentication. That only prompted a username/password request, which did not work.
What am I doing wrong here? I assumed having no authentication setup in the deployment would make the website open to anyone on our network. Not the case?
Found the problem(s) with this one.
Problem #1
When I downloaded / installed Microsoft's Web Platform Installer on my IIS server, the LightSwitch application I was working on and several other seemingly random websites/apps in the IIS all had the Authentication settings disabled for every authentication type (Anon, Basic, Windows, Forms, etc.). Had to go and Enable windows authenication on several websites. Did not expect that...
Problem #2
HTML Client folder was not loaded on the machine for some reason. Removed Lightswitch app from IIS and deleted the folder. Created a package for install in VS2013 and then copied the zip file over to the IIS server. Flawless install after that... One thing to watch for it to change the default setting in IIS from 'default.htm' to 'default.aspx'.
Is it possible to use SSL with Visual Studio Development Server (a.k.a. Web Application project)? I don't want to have to deploy IIS locally if possible. I'm running Windows 7.
NOTE: I've seen this (http://connect.microsoft.com/VisualStudio/feedback/details/354576/add-https-support-to-visual-studio-asp-net-development-server) but I was still hoping there was a workaround.
It cannot be done with VS 2008, so I've simply resorted to deploying my app to the local IIS as part of the start process with a generated cert.
We can use IIS Express with VS 2010 to develope and test web apps in SSL. Here is a complete article explaning how to use IIS Express and Visual Studion 2010 to develope websites in SSL
Working with SSL at Development Time is easier with IISExpress
Introducing IIS Express
this subject was covered here and it say's, you actually can't.
But you might take a look at this link, which might prove the contrary: (See link in comment, i'm not yet able to post more then 1 link per post ...doh)
Hope this helps.
It can be done in VS2010, I'm not sure if VS2008 supports the following approach. Configure Visual Studio to use use Microsoft IIS Express instead of the web server built in to Visual Studio.
well, according to what I've found googling around, it's imposible... (maybe with with windows xp 64...)
but I thought that maybe someone could find a way to achieve it, or at least some workaround...
http://www.iisanswers.com/IISFAQ.htm
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.inetserver.iis&tid=14654991-875f-4cc6-a853-7e9f3bb96bc3&cat=en&lang=en&cr=&sloc=en-us&m=1&p=1
--
ps: I need to debug classic asp code, and my production environment is windows 2003, while my development machine is windows xp...
--
edit:
just to clarify, I can already debug classic asp code in iis 5 with vs 2003 and 2008, it's just that I stumbled upon a (very silly) bug that only appeared on iis 6 (when IIS 5 received and empty http status, it just assumed 200, while iis 6 kept asking for my credentials in an infinite loop, it was very silly in deed, but took me a lot of time -and cursing- to discover it)
IIS 6 cannot be installed on Win XP. However, debugging classic ASP code is possible on Windows XP / IIS 5.1 using Visual Studio 2003 and up. You will need to configure IIS 5.1 to "enable ASP server-side debugging" (disabled by default):
IIS settings http://www.freeimagehosting.net/uploads/f1a6f781b9.png
Here is a more detailed article on how to debug classic ASP pages in Visual Studio - link
(NOTE: When running on XP Pro/IIS 5, you need to attach to dllhost.exe instead of w3wp.exe)
You posting in your 2nd link is correct. And read the faq. That spells out why it can't be done.
One option you can do is have a virtual machine of Server 2003 running on your laptop.
We have an application that starts a WCF server and the app reads from it.
It starts and can be read fine on all Windows XP machines.
On our Vista machine, however, we get:
System.ServiceModel.AddressAccessDeniedException
"The process has no rights to this namespace."
System.Net.HttpListenerException
The URL is at localhost:
http://localhost:8731/ABC.Testing.Business.Core/SecurityService/?wsdl
The error message sent us here:
http://msdn.microsoft.com/en-us/library/ms733768.aspx
And we did what it said:
netsh http add urlacl url=... user=...
which changed the rights but the WCF service still cannot start on Vista.
Does anyone have any experience with this that could move us forward? Thanks.
I had a similar issue with Windows 7 running Visual Studio 2010. My solution was a simple WCF service library with a simple console project serving as the WCF service host.
My base address in app.config was "http://localhost:8080/BookService" and I forgot that I had to start Visual Studio as an administrator in order to get Windows to map that port to my app.
As soon as I started Visual Studio as an Administrator (right click, Run as administrator) it ran like a champ.
try reading through this blog post and see if it helps.
http://blogs.msdn.com/paulwh/archive/2007/05/04/addressaccessdeniedexception-http-could-not-register-url-http-8080.aspx
I was having the similar problem while running the Project in VS2013 on Windows 8 OS, this problem get solved when I started my project as administrator..
Try to start up your app as administrator.
Thanks
Mayank Nagar