I'm following the Microsoft docs for SPFx https://learn.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/get-started/serve-your-web-part-in-a-sharepoint-page
and I am not able to deploy the app properly. Well it deploys, even gets listed as deployed (the WebPart), but it will not show up when I try to modify pages.
Has anyone experienced this before?
Any help will be appreciated, thank you.
You will need to either add your app manually to the site, or set "skipFeatureDeployment": true, in config\package-solution.json for the web part to be available.
Note, the last method deploys the app to all sites and thus makes the web part available for adding across your whole tenant.
Related
I have Kudu running nicely on IIS, unfortunately, I have one small problem. There is currently an orphan site which Kudu won't let me manage. I can find no trace of the site on the server and when I try and go into it or delete it from the dashboard I get:
Operation is not valid due to the current state of the object.
I can't seem to work out where Kudu is storing the details of applications that it knows about so that I can go in and edit them. Can anybody help?
Thanks
Chris
I still have no idea how my orphaned site got on there but deleting all sites has fixed the issue.
I am publishing the site using VS 2012 Publish website option. But the site does not get updated. I have to restart the website from manage.windowsazure.com every time after publishing.
I have been running the website on both free and shared mode. Same situation in both mode.
Any suggestion how to update the website automatically after publish?
Mmm. If your change regards CSS and JavaScript, try browse your website by using Ctrl+F5. If it seems totally not being updated, you might need to check the deployment page of your website on azure portal to see if it's get updated or not, or something wrong.
HTH
I have created a custom list in SharePoint 2010 programmatically. It works fine on my development machine when I deploy the project (that contains the list) to the SP site on my machine. I can see the list being deployed under lists. But when I package the whole solution and deploy the solution to test site on our test server on another machine the list seems to be missing on that sever (it does not exists under lists on that site).
There are some other custom lists within the project which are fine and are deployed properly but this one is not.
I finally managed to fix this mystery to my relief!
The problem was the feature that was supposed to put the list on the SP server, did not do its job.
When I first created the custom list in VS, I added it to an existing feature in the solution. But for some reason which I still cannot understand, the feature did not put the new list on the server. But when I created a new feature and added the list to it, it did put the list on the server when it got activated.
I compared the two features together. They both have the same properties. The only difference is the existing feature includes some more items to deploy and has an event receiver associated with it though the event receiver does not do anything that could prevent the new list from getting deployed.
I cannot understand this behaviour and would appreciate an input if someone can explain it to me.
I hope this will help other people who might come across this issue before they start banging their heads against the wall!
It is solution deployment type. Press F4 when in Package.package. Set "Deployment server type" to WebFrontEnd.
I'm developing sharepoint workflow inside which I call custom web service. Where can I put the configuration file (section), so I can change the url in the future for the web service? With the default one is working fine.
Thanks
Please refer to this question Access config file from a VS Sharepoint Workflow which has been already answered
You can also use an association form for your workflow. That has worked pretty well for me.
Does anyone have any idea how to deploy an InfoPath Form (2007) as a Site ContentType programatically (script or object model)? I do not want the form published to Central Admin and FormServerTemplates, but rather a Forms Library created by a Web scoped feature. The intention is to be able to publish the form via script or code in order to deploy and test the form in dev/stage/prod environments.
Well, I had to cut bait. Seems the two links provided a workable solution for now.
Sahil Malik's articel here provided enough information to deploy the form and the data connection was a simple matter of adding a module to the elements file for the feature. Some tips for this can be found here
Howerver, it seems there is no way to deploy a form to anything other than a Site Feature. After diving into the assembly Sahil mentions with Reflector, there is a check in the code to ensure the Feature is Site scoped. Arrgghh. If anyone can explain why this is, and perhaps an alternative, I would greatly appreciate it! Hope this helps someone else.