Where can I find release notes for FSharp.Core packages (https://www.nuget.org/packages/FSharp.Core/) ? I visited project's site on GH, but apart from a discussion on where these should be put I haven't found much more.
I'm mostly interested in differences between 4.7.2 and 4.7.0.
These are the GitHub repository release notes:
https://github.com/dotnet/fsharp/releases
https://github.com/dotnet/fsharp/blob/master/release-notes.md
They both seem pretty unmaintained.
Related
What is the difference between umbraco and vanila umbraco.
i'm currently using umbraco 6.2.1 version in my website.
Any special procedure available for upgrading this version to Vanila umbraco version.
Vanilla Umbraco means a fresh clean installation of Umbraco, without any customization.
Vanilla is a general term used for software, see also on wiki
Related to upgrading, one approach is to do a new installation of Umbraco (we can called it a vanilla installation) and then deploy your code, and migrate the content. Instead of the General Umbraco upgrade instructions.
I'd say that there is no running website with a vanilla Umbraco install. Umbraco is not a typical CMS. You are customizing it as soon as you start setting up your site in it. This is partly due to a choice on the Umbraco HQ team's decision to store their settings in the same files where you change settings by using Umbraco, requiring you to merge certain files during the upgrade.
As for upgrading, I'll warn you, there are a few ways to install Umbraco (Web PI, Nuget, Zip file), and if you upgrade in a way different than you installed, it can be hell. Step one, back up your site (front-end file-system files and db)! If you did not install Umbraco via Nuget (in Visual Studio), do not upgrade via Nuget. You will regret it.
Umbraco upgrades are a problem.
If the versions are minor running the update-package umbracocms nuget might work, but it often leaves the project mismatching version assemblies elsewhere.
Upgrading Umbraco is a bit of a minefield. Soz
Umbraco is now at version 11 and have moved their code base from the .NET framework into .NET core. Newer version is offering so much more, block-list, block-grid, inline editing, so many new and improved property editors. Editing experience and working with the CMS has changed so much since version 6.
Vanilla Umbraco would a term for a non-configured, fresh install.
You can find out everything you need to know about Umbraco on their documentation pages.
https://docs.umbraco.com/getting-started
Umbraco is a free open source project so there is no cost if you want to roll your sleeves, dig in and move over to the newest version. There are some paid offerings as well that would give support if you needed it.
Now that they have moved away from the .NET framework and moved their code base over to .NET Core there is no longer a direct path to upgrade from version 8 and earlier to the most recent version 11.
I would recommend you set up a fresh install, configure and customize as desired and then move any relevant content over to your new site.
There are many articles out there detailing how others moved over to the newer version.
Good article here on how they upgraded from version 7 to the newer version 11.
https://skrift.io/issues/how-i-upgraded-my-umbraco-v7-project-to-umbraco-v11/
Worth the read if your planning on going down that path.
Good luck.
This question is about how to set up a project template to satisfy dependencies.
First, some context.
I have a MVC4/Durandal project that I'm trying to turn into a project template that distils all the goodness from a recent project, for re-use.
After creating a new project, adding all the non-standard good bits and shaking down the stub project so that it compiles and runs properly, I copied the project folder and plonked it on another computer with a freshly minted VS2013 installation, to see what broke.
The following were MIA:
Antlr.Runtime
System.Net.Http.Extensions
System.Net.Http.Primitives
System.Web.Optimization
WebActivator
WebGrease
There are a couple of issues making it less than obvious to me as to how I should proceed.
Installation of these things happened so long ago that I really couldn't say how they got onto my development workstation
In many cases package dependencies mean that installing one NuGET package will implicitly satisfy other dependencies
I don't know how set up a project template so that it causes NuGET package(s) to be installed
A bit of guidance would be appreciated, not to mention advice on best practice.
Update
It appears there is direct NuGet support for project templates, I'm still reading about it here and also here.
Since allowing NuGet to automatically resolve dependencies is a good way to ensure compatible versions are installed in the right order, the remaining question is looking at the missing assemblies, how can I determine the most dependent package(s)?
It seems that omitting the packages folder produces a slim template, and the projects produced therefrom install the missing files as soon as you start a build. That's good enough for me.
I would simply start with a blank ASP.NET 4.5 MVC project. The most basic dependencies should be satisfied then. NuGet has basic packages for Mvc and other packages you may need. NuGet packages are designed to self contain the missing assemblies they need. They'll get published in IIS when you deploy so you don't install anything on the server.
It looks like the SongBeamer site which put up some nice ports for the TurboPower OpenSource projects for Delphi 2009+ are now being outdated with some recent updates in SourceForge. But, then again, maybe not? Which versions are best used with Delphi XE?
I'm most interested in Abbrevia, LockBox, and Async Pro. It looks like Abbrevia-SourceForge, AsynPro-SongBeamer, LockBox..?
I am the "owner" of the Turbopower projects on SourceForge. They are all in various states of development, but the most popular ones are XE ready.
I confess that I don't know the exact state of any individual project, but I can say that SourceForge is the best place to get the most recent and up to date "official" version.
As far as I know, the SourceForge versions of the projects are currently actively being maintained, under the direction of Nick Hodges.
Abbrevia is much better on SourceForge. The SongBeamer version was based on unstable code from mid-2008. I started maintaining the project in 2009 and the official 3.05 stable release had a lot of cleanup and fixes after that. v4.0 was released in March 2011, and added new features, include full support for Unicode filenames in zips, bzip2 archives, and decompression support for most of the new zipx compression algorithms (LZMA, bzip2, PPMd, WavPack). The current Subversion trunk also has Zip64 support and much better splitting/spanning support.
Async Pro appears to be better on SourceForge, but it's a bit of a mix. Officially only a handful of components have been updated to Unicode. In the SourceForge release the admin added $IFDEFs to keep the remaining files from compiling, while on SongBeamer they may still compile but might not be correct. There have been a few releases on SongBeamer since the SourceForge 5.0 release, so there may be some fixes not in the official release, but it's not based on the 5.0 release, so they're both missing stuff.
LockBox 2 is better on SongBeamer. The SourceForge version hasn't been updated with Unicode support at all. The SourceForge site does include a LockBox 3 project that supports Delphi 2007 through Delphi XE, but it's entirely new, incompatible code, so the only thing they share is the name. It is being updated though, unlike LB2.
Orpheus is better on SourceForge and incorporates all of the fixes from SongBeamer.
Office Partner has had a Unicode update posted in the SourceForge project's forums, but doesn't have a maintainer, so it's not official released or in the SVN repository. Not available on SongBeamer.
OnGuard and SysTools are the same on both sites.
ShellShock has Unicode support in the SourceForge Subversion repository.
XML Partner has the SongBeamer code committed to the SourceForge Subversion repository.
TP Essentials is better on SongBeamer.
The rest of the TurboPower projects SourceForge projects are dead.
Stay away from LockBox. Version 2.x in now really outdated (but for very simple cryptography needs), while version 3.x developer has somehow "stolen" the LockBox name, writing another library not compatible, and its quality doesn't look good.
Moreover IMHO he has no rights to change the license, only the Initial Developer - Turbo Power - can relicense under different ones, if he didn't like MPL 1.1 he could have created his own library without taking Turbo Power's Lockbox name and Sourceforge project. Thereby you may end up using a library with an invalid license, especially if you plan to use it under GPL terms.
If you have needs for good cryptography look elsewhere.
The sourceforge version of AsyncPro doesn't add the BCB components either - these seem to have suffered a lot since TP opensourced. I had to build packages for this a couple of times to support various versions of RAD studio. Haven't checked the latest songbeamer build.
Which is better source control with NetBeans (Ruby on Rails), VSS or subversion?
I want to use source control, so I want to know which is better for NetBeans (RoR). Visual Source safe or Subversion?
Absolutely Subversion.
I'd explain why, but Jeff Atwood has done a great job already and the blog entry links to other sites with great information.
Avoid VSS like the plague. You are far better off with SVN or Git.
I can give you the recommendation to use Subversion if possible. Even according to Microsoft, SourceSafe is a rather limited version control system. It lacks quite essential features such as transactional commits/revisions, branching and merge support, an easily corrupted database etc.
Alan de Smet has put up a rather long list here:
Visual SourceSafe: Microsoft's Source Destruction System
If you for any reason have to live with VSS make sure that you install all service packs and updates as there are a number of highly critical issues in the RTM version (e.g. this update, updates don't come automatically with Windows update).
Anything but SourceSafe. In all seriousness though, Java-based IDEs such as Netbeans, Eclipse and IDEA usually have the best support for Subversion. It's free, and it's fast, and it's solid.
The Subversion Netbeans module is provided as part of the platform and is more likely to be supported than the VSS one.
I don't think you should let an IDE to decide for you which Source ( Control program to use. If anything, it should be the other way around, but best if the decision to choose each (IDE and source control) are decided by its own merits. In case the chosen IDE does not have tight integration with the source control, it's not the end of the world or a show stopper. In other words, you can still be very productive if they're not integrated.
Be careful using any source control within Netbeans.
You need to be very cautious about ensuring that you stick to a version of Subversion that your version of Netbeans supports. Assuming you are using windows you will probably also install tortoise and it constantly checks for tortoise & SVN updates which you may foolishly opt to do and then suddenly your netbeans subversion integration is screwed up.
If you search for netbeans subversion plugin a lot of the top entries include the words "upgrade" and "broke".
My advice would be to avoid the IDE integration altogether. You reduce the number of things that can break and interfere with your work. If you learn the command line options you become platform/ide independent.
I gave up on SVN in Netbeans a while ago after getting frustrated with the constant fiddling with the plugin, netbean versions, and svn versions.
I have used subversion with Netbeans before and it is very effective - subversion allows you to keep your source organised in a nice, simple folder structure whilst being almost universally supported. Besides all of the VSS haters out there, SVN is almost certainly the best "traditional" versioning system out there.
Update 2019:
the Subversion support page date from 2013, for SVN 1.8
And the request for SVN 1.9 (opened in 2015) is still pending.
So using the Git Netbeans integration is a good choice.
As an aside, Ruby itself just got migrated from Subversion to Git.
The initial request for that migration was opened three years ago, and at the time rejected.
But bugs.ruby-lang.org issue 14632 opened one year ago (March 2018) went through.
As announced in "Ruby Repository Moved to Git from Subversion" (April, 23rd 2019),
Today, the canonical repository of the Ruby programming language was moved to Git from Subversion.
The web interface for the new repository is https://git.ruby-lang.org, and is provided by cgit.
We can keep the commit hash from the contributor on the Ruby repository directly.
I have a small ASP.NET MVC application developed using the latest beta version.
What would be an easy to follow step-by-step guide to upgrade to the RC released yesterday?
What key changes would I have to apply to get it working in the new version?
Read the release notes, the steps to follow are listed there.
Repeated here for your convenience.
There are not many changes between the Beta and the RC releases. However, you will need to make a few changes to your applications after installing the Beta release. Most of these changes are apparent when you try to compile your application by using the latest release, so we do not list every possible change.
The following list describes some of the changes that you must make.
Update the references to the
following assemblies to point to the
RC versions:
System.Web.Abstractions.dll
System.Web.Routing.dll
System.Web.Mvc.d
ll
Note If you are running ASP.NET 3.5 SP1, you need to update only the System.Web.Mvc assembly reference.
By default, these assemblies are located in the following folder:
%ProgramFiles%\Microsoft ASP.NET\ASP.NET MVC RC
After you have made these changes, compile your application and resolve any compilation errors. Most of the errors will be the result of one of the breaking changes listed earlier.
Update the section the Web.config file In the Views folder to match the following example. (The changed elements are in bold.)
I think the release notes has a fairly good guide.
There's some issues not mentioned in release note. Read this for more info:
http://forums.asp.net/t/1377139.aspx
You also make sure to add the following tag to your web.config file:
<system.web.extensions/>
It took me a lot of effort to figure it out since it's been nowhere documented.