Question: I wanted to ask if it is possible to use an inout pin as inout and normal out? The two behaviours should be switched through a MUX. The reason for this weird looking implementation is that I have two boards and I want to use the same bitstream. On one board, the same pin is connected to a LED through GPIO and on the other it goes to my I2C bus connection. The software tries to detect the I2C and if successful it sets a register. If not, it clears it. 

```
LED_or_SDA      : inout std_logic; -- port definition

process (register)
begin
   if ( register = '1') then -- software sets this register
       LED_or_SDA <= I2C_SDA; -- here I want to use it as inout
   else
       LED_or_SDA <= gpio_reg; -- here I want to use it as normal out
   end if;
end process;

```

This implementation throws the error "bidirect pad net is driving non-buffer primitives" during translate. Is there a solution for this?

Answer: 
Microsoft did clarify the position on No Code Sandbox solutions - <http://blogs.msdn.com/b/sharepointdev/archive/2014/01/14/deprecation-of-custom-code-in-sandboxed-solutions.aspx>

Also if you are looking at using Powershell to deploy then you might want to go down the route of using CSOM from within PowerShell - SharePoint Client Browser for SharePoint 2013 is good for setting up a session also very good for viewing the content of a 365 tenant - <http://spcb.codeplex.com/>
I have been using code based provision for almost two years without any issues at all.
Server side model works just fine, CSOM has some limitation but stil cool one and JSOM could deliver the same feature set as both CSOM and SSOM, sorta 95% :)

PowerShell is not the best option as it hard to integrate into CI, put some unit testing and regressions.

As you mentioned, this is "step back", but if only you don't have any framework or foundation for that. My libraries are internal one, but there is SPGenesis at codeplex and SPMeta2.
As community don't really care, need or with such libraries for provisioning (yep, let's face it), there are much such libraries at all, but there are lots of "MVP" samples sorta "hello world" level.

Finally, what I would suggest is to invest your time and effort in code based provision.
This is a future, that's it ;)

**UPD**

Struggling with SharePoint's API inconsistency, bugs, "by-design" behaviour, unaffordable amount of time to write, support and upgrade WSP packages and XML, a team of passionate SharePoint professionals decided to come up with robust, testable and repeatable way to deploy such artifacts like fields, content types, libraries, pages and many more.

Enjoy and let us know how it goes.

* [SPMeta2 at GitHub](https://github.com/SubPointSolutions/spmeta2)
* [SPMeta2 at Nuget](https://www.nuget.org/packages?q=spmeta2)
* [SPMeta2 Documentation Wiki](https://github.com/SubPointSolutions/spmeta2/wiki)
* [SPMeta2 Bugtracker](https://github.com/SubPointSolutions/spmeta2/issues?milestone=3&state=open)