Urgent: SMO 2012 - Issues

Question

So,
Yea, I asked a question about how to make sure that SMO/RMO would work when coming from a 2008R2 system to support 2012/2014 SQL Server systems.  I received assistence in the form of assurances that SMO/RMO in the 2012 redist would be fully backwards
compatible, with other in documentation assurances from MSDN that this would be generally easy to accomplish.
First Complaint:
I run the SharedManagementObjects.msi, which says "older version found, update" and I say yes, as backwards compatibility is assured, so even though my SQL Server is 2008R2, these 2012 objects should be fine.  But, where did it update too? 
I open Visual Studio 2012, open the solution, go to the references, click "Add Reference", but underneath "Assemblies | Framework" there are
ZERO assemblies that start with Microsoft.SqlServer.*  Hell, any search for SqlServer only provides a couple of listings under COM, which these assemblies aren't, so where did they
go?  In Program Files under the Microsoft SQL Server folder, there are no new additions, still just the same 100, 110 folders, and other associated data and report folders for those versions, but nothing to indicate a new installation of 2012 objects. 
Even so, if I navigate  to C:\Windows\Assemblies, there are quite a few of these files, many of which I need to reference, but they aren't showing up in Visual Studio unless I browse.  If I'm installing to the GAC that seems to be defeated by browsing? 
WTF?  However, many of them are listed at 10.0.0.0 version and others are listed at 11.0.0.0 version.  So did this install or not?  How can I reference the 2012 specific versions now that it's installed, and include the redist so that my clients
can use my software?
Second Complaint:
Again and again How many times I've stressed I need RMO!!!!!!!!  I downloaded the SharedManagementObjects.msi and opening it up in Orca, there is
NO listing for a Microsoft.SqlServer.Rmo.dll
assembly.  None, zip, zlitch, nada, bupkis, you name it.  I go to the MSDN help, and the objects like:  MergeArticle, MergeSubscription, MergeConflictCount.  All of these classes
are described by MSDN to exist in Microsoft.SqlServer.Rmo.dll (even for the 2012 and 2014 editions), and yet the 2012 redist doesn't have that assembly.  So what kind of false, misinformation is MSDN providing for supposed backwards compatibility, when
2012 doesn't have the primary assembly dll, and 2008R2 RMO fails on SQL Server 2012, not to mention where the hell these things install too, which is
not  the same GAC as visual studio is using.
*sigh*
SQL Server 2012 Deprications
Is that it?  Is RMO dead?  If 2008R2 RMO assembly can't connection to 2012 SQL server, then we're hosed and I say "thank you very much Microsoft".  If not, then why the confusion? Why the double speak, and misleading information? 
Why say on the MSDN that the objects still exist in 2012 & 2014 if they don't?
This is very frustrating, because we must be able to support replication, and if I have to tear everthing apart and dump the SMO/RMO
objects to manually code all the SQL commands, I'd rather know now and get started, which will be a veritable NIGHTMARE to debug and test without RMO, so to that I say: Typical Microsoft, shooting themselves and everyone who uses their products squarely in
the foot, but at the very least be honest and not lie to people saying, "oh that will work" when it @#$%#$% doesn't.  
Regards,
Jaeden "Sifo Dyas" al'Raec Ruiner
Previous Thread Regarding SMO/RMO:
Deploying RMO/SMO Applications
"Never Trust a computer. Your brain is smarter than any micro-chip."
PS - Don't mark answers on other people's questions. There are such things as Vacations and Holidays which may reduce timely activity, and until the person asking the question can test your answer, it is not correct just because you think it is. Marking it
correct for them often stops other people from even reading the question and possibly providing the real "correct" answer.

Answer 1

First, when you install SMO there is a folder (depending on the platform x86/x64) called c:\Program Files\Microsoft SQL Server\110\SDK\Assemblies.  This is where the assemblies are placed when you install the SMO objects.
Second, the RMO is a deprecated dll and now you will find the Replication stuff in Microsoft.SqlServer.Replication.dll it is in the SDK folder as well and can manage Replication.
RMO is no longer a separate product/download, it is all included in SharedManagementObjects.msi.
I hope this helps you out.
Ben Miller - SQL Server MVP, SQL MCM 2008 - @DBADuck http://www.dbaduck.com