New answers tagged solution-deployment
As Far i Know, if all developer using the same account at different times then they can deploy the apps to the Office 365. Check below link for more information. http://community.bamboosolutions.com/blogs/sharepoint-2013/archive/2012/08/14/how-to-deploy-apps-to-office365-preview.aspx ...
My assumption about variable count limit was correct. You can have 50 variables per activity, in my case Sequence. More on conducted analysis: http://slavensemper.blogspot.com/2014/12/maximum-number-of-variables-per-activity.html
I found a Solution for this case. While using the attributes UseDefaultListFormWebPart="FALSE" or UseLegacyForm="TRUE" did not add the default form webpart, SharePoint threw an UnsafeControlException. It looks like the DataFormWebpart on my NewVisitor.aspx could not be used "standalone" this way. The final solution was following: Open ...
I was able to use a custom form in place of the default one, without duplicated fields by applying the attribute UseLegacyForm="TRUE" on my custom form registration. In your case that should become: <Forms> <Form UseLegacyForm="TRUE" Type="DisplayForm" Url="DisplayVisitor.aspx" ...
The DLL you are trying to add is most likely a 32-bit DLL. SharePoint development is done in 64-bit and thus it is not possible to use that DLL in your application. That also explains why SharePoint is not able to load your DLL since you only have the 32-bit DLL installed in your GAC after deployment.
Top 50 recent answers are included