chrishasz / spgo

SPGo: A Lightweight, Open Source, SharePoint IDE for Visual Studio Code
https://www.chrishasz.com/spgo
MIT License
60 stars 11 forks source link

Only part of my code gets migrated #77

Closed kenhughlee closed 5 years ago

kenhughlee commented 5 years ago

I don't know if this is a VSCode issue or if just part of my code didnt get migrated, but wherever I have XSL code, the rest of the code gets cut off. Do you know why this is happening?

sg-chrishasz commented 5 years ago

Hello @kenhughlee - What kind of files are you having these issues with? (e.g. .webpart defnitions, with embedded xsl, pure xsl files). There are some types of SharePoint files, such as content pages, which store partial data in the contentDB and I want to make sure this isn't a SP-native issue.

Can you give me an example file so that I can replicate this issue locally?

Thanks!

kenhughlee commented 5 years ago

I emailed you.

sg-chrishasz commented 5 years ago

Hello @kenhughlee - Thanks for sending over all of the files. If I understand correctly, you are editing/adding web part or markup directly to a the content region of a page in the pages (or sitepages) library.

Unfortunately this is one of those SharePoint outliers - all of the content in pages is actually stored in SharePoint's ContentDB and would require additional webservice calls which are not currently supported by SPGo.

Since you are working with a DataForm Webpart, my recommendation would be to create this as a custom webpart in the webparts gallery. You can then edit/modify this web part using SPGo by synchronizing the _catalogs/wp folder of your SharePoint site. Also, this allows you to reuse this webpart easily across sites or pages. I've used this same method successfully in the past to manage custom webparts on pages.

Thanks!

kenhughlee commented 5 years ago

Okay. Thanks for looking into that.