I've created a simple asp.net application to open a site and display the title of the corresponding web. But i'm getting FileNotFoundException while trying to open the site. The same code works perfectly when i run it in a console app.
My spec
Windows Server 2008 R2 x64,
SharePoint 2007 x64,
Visual Studio 2005
My target for the asp.net app is set to 'Any CPU'.
As far as permissions is considered i've checked that the current identity using under which VS2005 hosts the asp.net app is having full rights. In fact i've used the same identity for app pools in IIS.
As an asp.net web application
As a console application
Any ideas?
Code
using (SPSite site = new SPSite("http://dev01/"))
{
using (SPWeb web = site.OpenWeb())
{
Response.Write(web.Title);
}
}
Right click on the solution -->proterties-->Debug-->Start browser with url->here provide the url (("http://dev01/").
When developing a solution for SharePoint 2007 with VS 2010 i'm getting this problem. When i create the same solution with VS 2005 i dont have any issues. I guess some of the dlls are mismatching between x86 and x64. Guess i would need to tweak a bit to make VS 2010 working with SharePoint 2007.
Related
I have just started to debug a Classic ASP website. The old development environment was running in a VM machine on Windows Server 2003.
I have created a new Windows Server 2003 R2 server and have transferred the website.
The site also uses 11 ActiveX DLL's written in VB 6.
I have moved them over and used regsvr32 on all of the DLL's to register them and all appears well.
When I try and view the web page however I get the Error:
MX error '800a01ad'
ActiveX component can't create object.
/includes/somefile.asp, line 16
If I create a basic asp page, the page is served from both the root of the website and the virtual directory /includes fine.
Thanks
Some other VB6 activeX dependencies were discovered. Registered them, now working sweet.
I am trying to host a asp.net razor v3 website to IIS, but it is not working. I tried multiple options including first creating the website then publishing to IIS, or directly creating a new website under IIS using visual studio 2013. It gives me HTTP Error 503. The service is unavailable.
Methods to reproduce Error:
Option 1
1) Create a new asp.net web site (razor v3) in visual 2013, and click publish to publish to a directory. Then, add that directory as a website in IIS.
Option 2
1) On the new website window, in visual studio 2013, go to browse and select IIS, and create a virtual directory directory under IIS to save the site.
Then, go to the browser and try to access the hosted site: localhost/sitename, it always produces some kind of errors. Like 503. What am I missing? Please help, looks like I am missing some steps or some configuration changes.
Also, I am trying this with the default razor v3 webiste content and without modifying anything. So, I have not touched any files or anything, I am just trying to upload to IIS.
The correct answer I found was that for some reason you must use the IIS Express 8.5 to test/host that site.
Even the installations on the fresh copies of Windows with Full IIS prior to version 8 did not work on my test machines.
I recently setup a sharepoint server 2013 on our company and have found really good examples how you can override the suitbar with custom links.
Now that I'm trying to implement those examples i get to that point where Visual Studio 2012 and Office development tools is installed.
When i choose to start a new project I select New Project > Templates > Visual C# > Office/SharePoint > SharePoint Solutions > SharePoint 2013 Empty Project hit ok and i get an error that says Sharepoint not installed?
Am I supposed to install VS 2012 and develop om my Sharepoint 2013 server directly?
A very common way to develop SharePoint applications is to run a virtual machine (hyper-v under windows 8 for example) on your development workstation.
You can also dual-boot into a vhd file.
You can also install Windows Server 2012 and use one of the many desktop conversion techniques to use it as your primary operating system on your workstation.
Another often seen technique is to have a virtual machine hosted in the cloud or a datacenter, running both SharePoint Server and Visual Studio. Then connect to that machine using Remote Desktop.
With some trickery, you could have the SharePoint 2010 installer install om a workstation OS. This no longer works on SharePoint 2013. The reason this support was removed is due to the inclusion of Boot from VHD and Hyper-v into Windows 8.
It is my experience that if you just want to build your application and not run or debug it, that just having the assemblies copied over from an actual SharePoint Server will allow you to do that. I haven't found an updated document for SharePoint 2013 yet.
Yes. You have to develop on the sharepoint server directly using Visual Studio as Sharepoint server GAC has the required server object models to work programatically with sharepoint server object model.
You can aslo develop on client machine using Client Object Model or WCF Data Services Framework.
I have upgraded my 2011 Lightswitch app to 2012 RTM and it works fine locally. However, when I try to Publish it to my web server it fails (http://blogs.msdn.com/b/bethmassi/archive/2011/03/23/deployment-guide-how-to-configure-a-web-server-to-host-lightswitch-applications.aspx).
I checked the Web Platform Installer on the live server and it does NOT have "Visual Studio LightSwitch 2012 Server Runtime without Local SQL" (http://msdn.microsoft.com/en-us/library/Gg481779(v=vs.110).aspx) - it only has the 2011 version.
Where do I get the 2012 version from? There is very little info about it on the web.
Ok, I am going to summarise my experience here as it might help others who are upgrading. My app uses the Telerik RadgridView control and Forms authentication. It runs OOB:
1) Firstly, I upgraded to the RTM LS2012 version and rebuild my app - all works fine on Dev.
2) I then tried to deploy to my Win2008 Server with no changes (note: it was running the LS2011 version with no problems). This failed with an "Unknown" message during the publish process. To get around this I unchecked the flag on the Publish wizard "IIS Server has the Lightswitch Deployment Prerequisites".
3) Next problem: The Silverlight App would show "loading" and then show a blank screen. At one point I received a message saying "Debugging resource strings are unavailable". The problem here was that the IIS site that the publishing wizard created had Windows and Forms Authentication (under the IIS Authentication icon). Disabling Windows Auth solved this problem. I was finally able to log on to my app.
4) Hardest problem: The app would log in and work fine for about 20 seconds. Then it would throw a Silverlight unhandled exception: "Unhandled exception at 0x5ceed700 in sllauncher.exe: 0xC0000 094: Integer division by zero". After a lot of Googling someone asked if I was using a VM - the server IS a VM and they suggested I run as a single processor (ie. it was a threading error). I did not try this, instead I tried running from a different PC as a client OOB (I was testing on the server). This then worked.
After all this my app is now up and running as Lightswitch 2012.... hope this helps someone!
Notes: I did NOT install .NET 4.5 (my projects target .NET 4) OR the Lightswitch 2012 requisites on the server. It works with the Silverlight 4 Telerik dlls.
I think all you need is change of .NET framework from 4.0 to 4.5 in your application directory.
It is called "LightSwitch for Visual Studio 2012 - Server Configuration with(out) local SQL Express" and available at the Web Platform Installer.
sorry for possibly a very stupid question.
I have one of those Visual studio Web Sites ( ie not a web application) ,
is there any way I can automate the creation of the IIS Web Application that points to the web site within Visual Studio ( ie then when developers open the solution, the IIS site will be set up automagically?
Sorry, just not famiiar with the Web Site side of things
Thanks
AFAIK It's not someting Visual Studio will do out of the box. What you could do is create a batch file that creates the virtual directory then opens the solution. Store it in source control and your developers will be able to run it instead of opening the solution directly.
There are a few options for creating an IIS virtual directory automatically - see this and this.
Also - if you are using VS2005 or above you could change you application to use the development web server instead of IIS and then you won't need to mess around with virtual directories at all. Select 'Use default Web server' on the 'Start Options' section of the projects property pages.