I am using Zurb Foundation V3 currently. Does anybody know if I upgrade Foundation V3 to V4 will V3 projects still compile using V3 gems/sass? Can the two versions of Foundation be used on the same computer for different projects or will I have to migrate all my existing projects to V4 if I upgrade?
Many thanks.
There is a migration guideline documented in Zurb's website. Your design will not change, at least it should not be, as things still work pretty much the same. But you will certainly have to change some markups. Take for example the classes for the grid which is, arguably, Foundation's heart.
About using different versions, yes I think it should work as long as you only use a specific version for one project, it doesn't matter if they are on a single computer.
Related
Is there a manual describing migration from Bot Builder SDK v3 to v4?
I have a lot of compilation errors after updating NuGet packages
Update
It appeared to be difficult. In addition to the answer below, I found this post quite useful to get a general picture https://blogs.msdn.microsoft.com/martinkearn/2018/07/17/bot-framework-v4-what-i-learnt-in-4-days-in-july-2018/
You can't just update your NuGet packages from V3 to V4, without changing your code. It is a major release with a lot of breaking changes.
The roadmap
for botbuilder-dotnet describes that a migration path from V3 to V4 is still in progress. I would suggest to have a look at BotBuilder-Samples and Microsoft Docs for the moment, to get an idea about how much has changed.
There are lot of changes from V3 to V4, they have completely re-written the concepts, architecture and terminologies.
So just updating the libraries won't work, you must update the code as well.
The roll-out is still not complete so it is recommended to use v3 in production as of now.
Upgrade is almost equal to the efforts of writing the complete bot code again. In case you are comfortable with your existing bot functionality and is willing to add new features which has nothing to do with SDK version, you can do this using Bot Channel Registration. Steps to do this is mentioned in a blog here - https://chatbotslife.com/microsoft-bot-framework-sdk-3-code-on-azure-bot-service-without-migrating-to-sdk-4-14afa3300887
This is a "Veracity Platform" question - which I guess has a fairly small audience.
I'm using the veracity platform's application generator (based on Yeoman) to generate a sample application for .net core 2.x, using node.js.
yo #veracity/veracity:netcore-webapp
This creates a good basic .net core 2.x MVC project. Is there a way to further specify that I want to additionally include the "React/Redux" project template, like I would when creating a project in Visual Studio? That way the client app and the front-end webpack stack get started for me, which is nice.
Thanks in advance for any suggestions.
We do not have these configurations included in the generator yet. Uservoice will be added to Developer.veracity.com soon, but for now you may forward such feature requests also in the github project of the generator. Open an issue, and I will see when we can get it in to the backlog.
https://github.com/veracity/generator-veracity
Brede Børhaug - Manager Veracity for Developers
Am trying to install SIGNALR to my asp.net project, but when adding the Nugets, it keeps pushing an error that the "Package xxx was restored using .NETFramework, Version=v4.6.1 instead of the project framework .NETCoreApp, Version=v2.0". I get this error on several Nugets. I tried to re-install all Nuget one by one but same result when I arrive at some particular one like SIGNALR.
I believe I might have something wrong in the setup, but as am new to asp.net, would love a pointer. Read the literature but could not find the answer to this issue.
It also looks like SignalR might only be available for netcore 2.1 later this year but am looking for a way to use it, in a simple app.
So a couple of things.
For the latest SignalR Core bits you need to be targeting netcoreapp2.1. Preview1 and later depend on that.
If you want to just experiment with SignalR targeting netcoreapp2.0 the alpha 2 bits use netcoreapp2.0. But just to be clear the alpha bits are just a public preview and should not be used for production applications.
The main thing here though is that you are using the Microsoft.AspNet.SignalR packages. Those will not work on Core.
I'm currently working on new projects and I'll be using the Foundation 4 Framework (foundation.zurb.com). I checked the web up and down but couldn't find a project (GitHub or otherwise) that ported the SASS logic of Foundation 4 to LESS.
I really like Foundation 4 and I would love to work with SASS but as reality forces me to not use ruby for development, I'm down to using the pure CSS version of Foundation 4. I would prefer to use it with less, which I can easily include in my PHP workflow and porting all the SASS goodness to LESS is quite a bit of work. I am fully aware that some parts of the Foundation SASS logic won't work with LESS, but that is a price I'm willing to pay.
I found a grunt project (github.com/jonschlinkert/grunt-refactor) that offers/promises some degree of porting logic but as I never worked with grunt/node.js before, I couldn't get that working until now.
Do you know of a Foundation 4 LESS port?
Someone tried to create a fork in Foundation3 that was done in LESS but they eventually dropped it. You can find full discussion about this here: https://github.com/zurb/foundation/issues/370. I don't know about any other porting to LESS attemps.
i want to port my application to CodeIgniter but i am wondering whether i should use their v2.0 or v1.72 (then when they release 2.0, upgrade it).
i have never used a framework before so i don't exactly know what implies when upgrading a framework: what does it mean practically - i just move the folders and it will work? or do i have to change a lot of settings, file structure etc? could someone enlighten me about the upgrade process.
and what would you use: v.1.72 or v2.0?
if i'm using the latest version, is there a good documentation for it somewhere so you can read about how to use the new features: packages, drivers and so on.
thanks
You can read about some of the changes in 2.0 here.
I would image the upgrade process should be straightforward as long as you do not use any features that are different/removed such as plugins. Just take your models, controllers, etc and drop them into the 2.0 framework. Then regression test you whole app, fixing any problems as you see them...
If you are selling this app or making something mission critical then of course v1.7.2 is the best choice. That said I have PyroCMS running on v2.0 and since some of my bug-fixes were merged it seems stable enough.
One should consider time frames for deployment:
If it is one week, then stick to v1.7.2
If it is three months, go with v2
Assuming three months is approximately to time for a release to stabilise?