|
Edhy Rijo
|
|
|
Group: StrataFrame Users
Posts: 2.4K,
Visits: 23K
|
Hi Larry, VS2017 has been undergoing a very extensive beta and RC test. The amount of changes are just incredible and I am sure some things may still need a few fixes but based on the new culture a Microsoft, this seems to be the best upgrade ever to Visual Studio. All my other 3party tools support VS2017, as soon as Ben add its support for SFv1 and SFv2, I'll be there to retire VS2015. I am working on big project and VS2015 is acting up frequently, so I can't way to start using VS2017.
Edhy Rijo
|
|
|
|
|
Larry Caylor
|
|
|
Group: Awaiting Activation
Posts: 592,
Visits: 3.7K
|
Edhy, I'm sure you'll be one of the first on VS2017 , but I think I'll stay with VS2015 for a few months. -Larry
|
|
|
|
|
StrataFrame Team
|
|
|
Group: StrataFrame Developers
Posts: 3K,
Visits: 2.5K
|
I'm glad that got you fixed. VisualStudio changed their shell implementation of ITypeResolutionServiceProvider from Microsoft.VisualStudio.Design.VSDynamicTypeService to Microsoft.VisualStudio.Shell.Design.DynamicTypeService. I can't find the assembly where the ITypeResolutionServiceProvider is actually defined, and the both service objects are _COMObjects, so I changed the internal type to Object and used Type.InvokeMember() on the object to get the services I needed from the provider. As for why the SyncFusion Assemblies would cause that error to occur, I'm guessing that they use the same provider and somehow get it to initialize differently than us, so if they initialize the provider first it was the type we weren't expecting.
I'm glad to hear about the SyncFunction PDF components. Trent's been working with one of their salespeople for a while on acquiring that for us for use in our upcoming document manager for our medial software. A PDF component is not something we want to write.
|
|
|
|
|
Edhy Rijo
|
|
|
Group: StrataFrame Users
Posts: 2.4K,
Visits: 23K
|
Larry Caylor (2/28/2017)
Does the new visx fix the VS2013 problem or does it just ignore the code element in BO mapper? If it doesn't address the VS2013 problem then there is no hurry from me to fix it as I can now move everything to VS2015. -Larry Hi Larry, Since VS2015 supports any .Net runtime, I would suggest you move your solution to VS2015. Also, keep in mind that VS2017 will be released next week on March 7.
Edhy Rijo
|
|
|
|
|
Larry Caylor
|
|
|
Group: Awaiting Activation
Posts: 592,
Visits: 3.7K
|
Hi Ben, I've been looking at this for too long  I cleared out the dll's, uninstalled the visx packages and re-installed everything again and all is well now. The new package ignores whatever it is in the Syncfusion.XlsIO.ClinetProfie dll that was creating a problem for BO mapper and PopulationDataSourceSettings for list views in VS2013 now works. -Larry
|
|
|
|
|
Larry Caylor
|
|
|
Group: Awaiting Activation
Posts: 592,
Visits: 3.7K
|
Hi Ben, I spoke too soon. It seems that some SyncFusion dll's cause problems some do not so I gave the new SF dll's a try. I uninstalled the extension from VS2013 & 2015, added the new dll's to the GAC and re-ran the visx package and now Object Mapper is grayed out in the SF menu. -Larry
|
|
|
|
|
Larry Caylor
|
|
|
Group: Awaiting Activation
Posts: 592,
Visits: 3.7K
|
Ben and Edhy, thanks for the quick reply. I've got VS2015 working. I created a simple solution with one BO and everything worked so I figured it had to be something with my VS2013 solution. It has 10 projects and after a little troubleshooting I isolated the source of the error to one project. In that project I use SyncFusion's File Formats product to programmatically create Excel files. Deleting the reference to the SyncFusion dll's and re-referencing them fixed the BO mapper problem  No sure as to why that worked as the project appeared to compile correctly under VS2015 so I'm assuming the reference was ok. I also re-installed SF v2. I'm using the SyncFusion product because the SF ExcelHelper tool didn't do exactly what I wanted. The SyncFusion product was just under $1,000 and also incudes tools for PDF, Word and PowerPoint files. I also considered GrapeCity's Spread for Windows, which looks like a really nice product but is more expensive and has more features than I need, including visual components. Does the new visx fix the VS2013 problem or does it just ignore the code element in BO mapper? If it doesn't address the VS2013 problem then there is no hurry from me to fix it as I can now move everything to VS2015. -Larry
|
|
|
|
|
StrataFrame Team
|
|
|
Group: StrataFrame Developers
Posts: 3K,
Visits: 2.5K
|
I swapped out the VISX with the fixes on the Posted Releases thread, Larry. Give it a try and let me know. Thanks.
|
|
|
|
|
StrataFrame Team
|
|
|
Group: StrataFrame Developers
Posts: 3K,
Visits: 2.5K
|
The first one is because we are trying to cast to the specific type instead of using the root interface that they both implement. I don't know that I ever tested the new package on VS2013. I can change that to the interface and recompile it. I just have to figure out what obscure VSShell assembly contains ITypeResolutionServiceProvider. The second one is interesting. There isn't anything on the CodeElement that will allow us to determine whether it has a name, so I'm going to wrap that in a Try/Catch and just ignore the element if it throws an exception.
|
|
|
|
|
Edhy Rijo
|
|
|
Group: StrataFrame Users
Posts: 2.4K,
Visits: 23K
|
Hi Larry, I have a new computer and tomorrow will be installing StrataFrame, so I would have a better recollection on that configuration. In the meantime, couple of things to review: - Make sure that the connection to the StrataFrame.mdb database is configured for StrataFrame.
- Make sure you follow the directions on installing the .VSX package, and manually registering the required assemblies using the VS command prompt as "Administrator".
- StrataFrame v2 has nothing to do with SFv1, so not need to worry about it. It is a complete separate assemblies and namespaces, so they can both co-exist beautifully.
Good luck, if you don't make it work by tomorrow, I will be configuring mine and will have better suggestions.
Edhy Rijo
|
|
|
|