Quick Note: Android Gradle distributions

Here is the link for list of all available Gradle Distributions with latest one being first.

Quick note: How to download Xcode DMG or XIP file?

You can find the DMGs or XIPs for Xcode and other development tools on https://developer.apple.com/download/more/ (requires Apple ID to login).

You must login to have a valid session before downloading anything below.

*(Newest on top. For each minor version (6.3, 5.1, etc.) only the latest revision is kept in the list.)

Xcode 10

• 10 beta 2

Xcode 9

• 9.4.1
• 9.4
• 9.3.1
• 9.2 (Last version supporting OS X 10.12.6 Sierra)
• 9.1
• 9.0.1

Xcode 8

• 8.3.3
• 8.2.1 (Last version supporting OS X 10.11.5 El Capitan)
• 8.1
• 8.0

Xcode 7

• 7.3.1
• 7.2.1 (Last version supporting OS X 10.10 Yosemite)
• 7.1.1
• 7.0.1

Xcode 6

• 6.4
• 6.3.2
• 6.2 (Last version supporting OS X 10.9.5 Mavericks)
• 6.1.1
• 6.0.1

Even Older Versions (unsupported for iTunes Connect)

• 5.1.1
• 5.0.2
• 4.6.3
• 4.5.2
• 4.4.1
• 4.3.2
• 4.2
• 4.1
• 4.0.2
• 3.2.6
• 3.1.4
• 3.0
• 2.5
• 2.4.1
• 2.3
• 2.2.1
• 1.5
• 1.0

SSIS: Cannot convert between unicode and non-unicode string data types

Best thing to resolve this to add Data Conversion transformations to convert string columns from non-Unicode (DT_STR) to Unicode (DT_WSTR) strings.

You need to do this for all the string columns.

Add a data conversion task between OLEDB and EXCEL Destinations and do string conversations like below for the columns you are using

.NET Core 2.0 will reach End of Life on October 1, 2018

.NET Core 2.0 was released on August 14, 2017. As a non-LTS release, it is supported for 3 months after the next release. .NET Core 2.1 was released on May 30th, 2018.

Upgrade to .NET Core 2.1

The supported upgrade path from .NET Core 2.0 is via .NET Core 2.1. Instructions for upgrading can be found in the following documents:

• Migrate from .NET Core 2.0 to 2.1
• Migrate from ASP.NET Core 2.0 to 2.1

.NET Core 2.1 will be a long-term support release. Its recommend that you make .NET Core 2.1 your new standard for .NET Core development.

'TRUNCATE_ONLY' is not a recognized BACKUP option.

In Microsoft SQL server 2000 and 2005, as part of the ‘BACKUP LOG’ command, there was an option to truncate the log file, without storing a backup to file. In Microsoft SQL Server 2008, this option has been removed, and you can now no longer use the ‘TRUNCATE_ONLY’ option when performing a transaction log backup.

The truncate only option is used to truncate the log file. This is generally done so you can then shrink the transaction log file, and recover the disk space back to the file system.

I ran into this issue, when we are migrating our servers from 2005 to higher version.

Msg 155, Level 15, State 1, Line 1
'TRUNCATE_ONLY' is not a recognized BACKUP option.

To truncate the transaction log file in Microsoft SQL Server 2008 or 2012 and above, without making an actual transaction log backup (possibly due to free space limitations), you need to change the recovery model of the database to “Simple”, and then change it back to “Full” (or “Bulked Logged” if that’s what it was previously).

USE ps;
GO

-- Truncate the log by changing the database recovery model to SIMPLE.
ALTER DATABASE ps
SET RECOVERY SIMPLE;
GO
-- Shrink the truncated log file to 1 MB.
DBCC SHRINKFILE (ps_log, 1);  
-- here 2 is the file ID for trasaction log file
--you can also mention the log file name (dbname_log)
GO

-- Reset the database recovery model.
ALTER DATABASE ps
SET RECOVERY FULL;
GO

Hope this helps.