Is it possible to add a static web folder as a project in Visual Studio?
I have a VS solution with a number of sites and services, I also have a static html/JS/backbone site with no .net/cshtml content which I would like to be logically in this solution, and edited in VS.
is this possible?
Create a physical folder with your web site in it.
then right click on solution, add existing web site, and select the folder
You could just add a new solution folder, and add your files under there.
Related
I have a small website written in asp.net c#. It consists of 7 pages or less, connected to a database and references a class library. How to convert it to a visual web part in sharepoint 2013? my colleague advised me of copying the codes from the website solution to a visual web part solution. The question is, is his suggestion feasible? are there any other ways of doing it besides iframes and my colleague's suggestion?
Your options depends on if your solution will live in a Publishing Portal or not. The most generic way would probably be to use a visual webpart and host it there. If you would like a more comparable version of this from your current solution you can build and deploy custom page layouts hosting your code.
I am new to sharepoint and have a scenario
1) I have a aspx page which displays some data from a xml.
2) The data is populated in a table in the aspx page using a code behind .cs file.
3) I use some dll's which I have made to access the data.
Note:- This things are done on my local pc which does not have a sharepoint server installed.
Now my question is
1) I want a way using which I can use this page as a webpart in a sharepoint site.
2) Can you please guide me a by which the compiled dll of the web application can be used as webpart.
Note:- I have access to put files on the server but cannot develop anything on that
You can use the User Control in SharePoint and add it to your site page..
OR
Use Visual Studio and create an empty SharePoint project (deploy as farm solution).
Then, right click project and add mapped layouts folder.
Rename this folder to whatever name you want to appear (this folder will get created on the servers layout folder in the hive) after you deploy the solution.
Add your aspx page and cs into this folder
Then, double click on package.package (its inside package, above layouts folder, under project)--> Advanced --> Add (existing assembly) and add your dll references here.(this will add the dlls under your sites sharepoint web.config.
After deploy, you can access page using: http://sharepointsite/_layouts/foldername/youraspxfilename.aspx
Let us know about the progress.
I am working with Kentico in Visual Studios (web project) on my local computer. When I add folders or files to the solution and then run it in the browser, the pages do not show up in the CMS desk or site manager. Am I creating these folders/files in the wrong place in the solution (ex: {directory of web project}/CMSPages/filename.aspx)? Or maybe have incorrect settings?
This is not the way how it works - the system has no idea about your pages if you place them on the file system. However, you can create ASPX page templates and then use then for the documents. Please see the Devnet forum
Best regards,
Juraj Ondrus
Where Do you want to use this page?
In the visitor sites or CMS Page
If you want to use visitor site you can create a webpart and add you webpart to the Page create on content tree.
If you want to use in the cmsdesk the you need to register your page in the module
I'm using Visual Studio 2010 to develop a SharePoint Server 2010 solution. Part of this includes custom Page Layouts, but when editing them, intellisense is completely broken, since Visual Studio doesn't appear to know how to handle them. Here's what I've done:
Created a new blank solution
Right-clicked on the solution and created a new "Empty SharePoint Project"
Right-clicked on the project and created a new "Module"
Renamed sample.txt to MyPageLayout.aspx or created a new ASPX Web Form
At this point, intellisense for the new Page Layout is broken. It gets even worse with tools like ReSharper installed. Also, things like "Format Document" will break the Page Layout (by for example changing asp:Content to asp:content)
What I've tried to get intellisense working:
Added a Web.config from a standard Web Application Project to the root of the SharePoint Project - made no difference.
Added the ProjectGuid for a Web Application Project to the SharePoint project file - broke the project.
Is there any way to get intellisense, and the rest of the support Visual Studio can offer for Web Forms, available when developing SharePoint 2010 Page Layouts?
I have followed your post to some extent.
Using VS2010 (On an x64 machine)
Create a blank SharePoint solution. (this properly combines your #1 & #2)
Add a module (in SharePoint a module is like a folder or resource container)
added a new class to the module (intellisense present)
Added a new webpart to the module (intellisense present)
added a user control to the project designer works and (intellisense present)
I believe that you should consider creating true server or visual web parts. This will have a harder learning curve but will pay with dividends in the future. You will be able to package and deploy your solution again or to another server/farm. Aspx pages can be added and manipulated by the dreaded SharePoint designer. In 2010 the theory is that those designer mods can be packaged and deployed.
I work in this environment every day and the best advice I can give is to embrace the SP object model and do 'it' the sharepoint way. Don't try to force SP to be something its not. :)
This is probably not the solution you are looking for but it's the best thing I found for SharePoint development.
In your solution, create 2 projects :
1 SharePoint Project (empty or not)
1 ASP.NET web application project
Develop all your UI (aspx pages, ascx controls, etc.) in your ASP.NET project and create post-build steps that will copy the pages and controls to the appropriate folders in your SharePoint solution.
That way, you will benefit from all the features of web development in visual studio and it will be very easy to deploy as well. It is a bit of a time investment at first, but it is well worth it if you have any considerable amount of logic to implement in your aspx pages.
This blog post documents what you need to do.
you can add an intellsense to pagelayouts by closing the page and simply reopen it from
file->openfile->your file page layout path
Or you can directly "Right Click" on the file you want to open from the Solution explorer and then select "Open" : you'll get the Intellisense !
I have only ever deployed web parts from development by clicking F5. Now, I know I have to have a manifest file, feature file, etc and it all goes into a wsp file. I understand the wsp file is what gets added to Central Admin.
So my problem is this. I have found lots of sites that show how to use WSP Builder, but they don't seem to show how/where I add my web part to the WSP Builder project. My understanding is that somehow I should be able to use WSP Builder to create a wsp file containing my already-developed web part.
There are only two approaches that I see would work.
I create a WSPBuilder project (like all the how-tos on WSPBuilder show), then I assume I would somehow add my web part to that project - although I don't know how.
In my web part project, create WSPBuilder -> Build WSP. I have done this, and when I run stsadm on the resulting wsp file, I get it in Central Admin, but its not added to my Site Collection Features or my Web Part Gallery.
Can someone please explain this to me like I am a 6 year old? If you point me to another site, there is a good chance I have already seen it, so then I would ask you point me to the specific lines that tell me how to get my already existing web part packaged into the wsp.
To create a new web part feature with WSPBuilder:
Right-click on the name of your WSPBuilder project in Visual Studioand click Add, New Item.
Select WSPBuilder from the tree on the left and choose Web Part Feature from the list on the right of the dialog.
Enter the title of the web part feature and click OK.
In the dialog that appears enter the title, description and scope and click OK.
Your feature will now be created. You will then need to merge your existing web part code into this feature and configure its XML files.
Read this walkthrough by Tobias Zimmergren for more information. There is another walkthrough here.
Alex, got the right path to solve it. I think the small exception here is that wrongly spelt Add New Item instead of New Project.