Is it possible to use Subsonic with VistaDB? I see it as a supported database for Subsonic 3 on the project website, But can't find a T4 template for it?
Will I need to use SR or I can use AR?
Vikas
Although the underlying architecture of SubSonic (System.Data.Common) supports VistaDB there aren't currently any templates for it. So although in theory it's supported it won't be supported in practice until someone creates those templates.
I wrote a vistadb provider for subsonic 2.x that was never made part of the official project. The main reason it's not in subsonic is that it's not freely available, the required dll for it is very encumbered with licensing. So no one wanted the hassle. You could take this provider code and use it to prepare a template, or just copy the sql server template, and make the required edits for reading the schema. I don't think that vistadb will ever be an official part of subsonic 3 since the vistadb dll is not freely available even for testing. I dropped vistadb because of performance issues.
Related
I'm trying to prevent cross-site scripting in the backend of my web-application. I was researching and I came accross the AntiXss nuget library. I noticed that there has not been a new release for a while. I was just wodering if it is recommended to user this library or if I should try a different approach.
In .Net versions 4.5 and later, AntiXSS is part of the framework and not a separate library anymore. It is in the System.Web.Security.AntiXss namespace, with almost all functionality of the original separate library.
Docs are here.
Compared to other built-in classes like HttpUtility, AntiXss is more secure, because it's a whitelist-based encoder, as opposed to blacklisting provided by other classes.
One part that did not make it into the framework is Sanitizer, but that was not very useful anyway. There are other libraries for html sanitization if needed (mostly not, it's a special case when dealing with user-supplied html code).
I am having a little problem in my workplace where we have a IIS 6 server where Orchard (1.7) will not run. We are planning an upgrade but that's going to take some time.
Since we are using this site on IIS6 only to run one particular custom module we wrote for Orchard (basically a MVC module with its own Controllers/Actions etc.) I was thinking that a temporary solution could be to rip that module out of Orchard and run it independently.
Of course this extraction needs to take into account how many ties I have with the framework. I was wondering if there is some kind of guide to perform this and if there is something I need to take specially into account.
I am using the Users in Orchard so I would probably have to rewrite some users code. I am also using the Authorizer, which again may mean I need to re-wire something else.
It seems like a daunting job so I am looking for some quick tips on how to proceed if you know any.
Thanks a lot!
It all depends on what components you actually use within your module.
Hard to write any tutorial on this, really.
Regarding Orchard.Users - you could drop all related code usages and rely on the default ASP.NET roles-based authentication/authorization model.
If dependency injection is what you want to keep, then you need to integrate it yourself (for Autofac, but other DI containers will also work). Feel free to copy and change any Orchard components that you use, stripping the unneeded code.
In my opinion the hardest thing to strip out and replace would be any code that relies on content items - hope you don't have it. Rewriting this pieces sounds like an overkill. But if you just use IRepository, going for plain NHibernate or EF instead should be quite easy.
I am planning to upgrade my company's intranet from liferay 6.0.6CE to 6.2CE. I have done some research on it but I am still confused on API part. Will my custom portlets need only recompilation or would they need a complete rewriting. I am also concerned about my Theme and Exts. I have a lot of customization in my exts and my theme. What would be the best way to move ahead?
Also I have a NFS file server and SOLR search server configured with my current deployment. Need suggestions on that too.
I've heard recently, that the Migration Tool (6.1 to 6.2) now also supports themes. It won't be pixel perfect though. Check what it can do for you.
There have been some APIs that changed. Contrary to the comments given to your question, I'd say "It depends": I don't know how much of Liferay's API you use or if you just add functionality on top. You'll have to find out for yourself. The migration tool might help you.
The things that have changed the most are: Themes (using Bootstrap, as of 6.2) and Document Library (now including ImageGallery, which was still available in 6.0). Migration of data should be smooth if you follow the documented upgrade path. Migration of your portlets and plugins will definitely require recompile (within the new plugins sdk or updated maven dependencies) and probably adaptation to some changed API calls. I've seen instances where this was simple, but I've also seen hard cases.
As there have been no more updates for 6.0 CE for quite a while, I'm recommending to upgrade though (other than #FeinesFabi in the comment). If you want to have a long-term stable platform that you don't need to maintain for yourself, EE would be the way to go (supported for ~7 years after release)
For ext changes, you'll have to be aware that there are no guarantees: Ext allows you to change the inner implementation of Liferay, and that's what nobody strives to keep stable, even in minor updates. If you're using ext, you'll always have to be aware of incompatible changes. Ext allows you to keep your changes out of the official sourcecode - so they're well isolated. It doesn't say anything about the underlying implementation to be stable. With great power (ext) comes great responsibility. Keep your ext as small as possible - whatever you can do outside of ext should be done outside and use the public API.
The basic upgrade path (for Liferay itself, not your plugins) is quite well documented in the User's Guide.
I am having trouble finding a NoSQL databases that officially support MonoTouch via a local DB on the device. If their are, could someone provide a list of them here.
According to http://nosql-database.org/ there's siaqodb. Note that others might support MonoTouch without being mentioned in that site.
Edit: a few more clicks shows that HSS Database (from the same list) also supports MonoTouch.
You might also want to look at which ones support iOS (e.g. with Objective C) and see if bindings are available (or write your own).
Take a look on Couchbase Lite xamarin's component
RavenDB supports an embedded mode, and can run on Mono using the "Munin" storage engine option.
Although, there has been talk in the user group lately about dropping Munin, and it's not usually recommended for production, so it may not be a viable option.
I've not heard of someone using it with MonoTouch specifically, but there are some running it on Mono. If you try it, please update comments here with your findings. Thanks.
A bit late, but still relevant:
I'm the author of MarcelloDB, and I just released version 0.3.0 on nuget.
MarcelloDB is a document DB, built specifically for mobile apps (light-weight, low memory usage) and supports Xamarin Android and iOS as well as the windows platform.
I still have some features I want to add before reaching v1, but the file format and existing api are allready quite stable.
(Warning: This may be a stupid question...)
I am am one of those who are not willing to move to SubSonic 3.0. I am currently using a customized fork of SubSonic 1.(?). I want to migrate to version 2 for many reasons, and I have been successfully been playing with Subcommander. Cool stuff! Here's my question...
When I generate the DAL for 2 databases, when I put those DAL files into the same project, with SubSonic 2.2 allow me to connect to both of them in the same project/application at the same time?
Yes you can, but they will need to be in separate namespaces (I think). I've done it and I found that giving each its own project and namespace was the easiest to manage - especially with subcommander since each project can have its own config file.
You may also want to take a look at the SubStage application. I found it great for discovering the myriad of settings available with SubSonic code generation.
Multiple database support was first introduced with SubSonic 2.0 Beta 1. It is hard to find samples online, but the Starter Site project is still a good reference as it includes two database references. You can find the source on Google Code.