Visual Studio Code doesn't support solution files, whereas Visual Studio does. In Visual Studio we use solution files to link multiple projects together, and at first I thought that this was going to be a deal breaker for Visual Studio Code - but it's not at all. Many people aren't aware that Visual Studio Code, although lightweight, is a powerful editor that can do most of the things you need.
sudo npm install -g bower bower init
bower install bootstrap-sass-official --save bower install fontawesome --save bower install bootstrap-rtl --save
sudo npm install gulp gulp-ruby-sass gulp-notify gulp-bower --save-dev
var gulp = require('gulp'),
sass = require('gulp-ruby-sass'),
notify = require('gulp-notify'),
bower = require('gulp-bower'); var config = {
sassPath = './resources/sass',
bowerDir = './bower_components'
} // create a task to do bower install
gulp.task('bower', function() {
return bower()
.pipe(gulp.dest(config.bowerDir))
}); 
// Copy js files to public folder
gulp.task('js', function() {
return gulp.src([config.bowerDir + '/bootstrap-sass-official/assets/javascripts/bootstrap.min.js',
config.bowerDir + '/jquery/dist/jquery.min.js'
])
.pipe(gulp.dest('./public/js'));
});
// Copy fontawesome icons to public/fonts folder
gulp.task('icons', function() {
return gulp.src(config.bowerDir + '/fontawesome/fonts/**.*')
.pipe(gulp.dest('./public/fonts'));
}); 
gulp.task('css', function() {
return sass(config.sassPath + '/style.scss', { // Our coustom sass
style: 'compressed', // minify css
loadPath: [ // load paths to easy use import in resources/sass
'./resources/sass',
config.bowerDir + '/bootstrap-sass-official/assets/stylesheets', // bootstrap sass files
config.bowerDir + '/fontawesome/scss' // awesome icons sass files
]
})
}); gulp.task('css', function() {
return sass(config.sassPath + '/style.scss', { // Our coustom sass
style: 'compressed', // minify css
loadPath: [ // load paths to easy use import in resources/sass
'./resources/sass',
config.bowerDir + '/bootstrap-sass-official/assets/stylesheets', // bootstrap sass files
config.bowerDir + '/fontawesome/scss' // awesome icons sass files
]
})
.on('error', notify.onError(function(error) {
return 'Error: ' + error.message;
}))
.pipe(gulp.dest('./public/css'));
}); // Rerun the task when a file changes
gulp.task('watch', function() {
gulp.watch(config.sassPath + '/**/*.scss', ['css']);
}); // Run this task with : gulp
// OR gulp default
gulp.task('default', ['bower', 'icons', 'css','js']);
Better late than never! Some of you may have noticed that C# 7.3 already shipped, back in Visual Studio 2017 update 15.7. Some of you may even be using the features already.
CommunityToolkit/dotnet: .NET Community Toolkit is a collection of helpers and APIs that work for all .NET developers and are agnostic of any specific UI platform. The toolkit is part of the .NET Foundation.
With the release of .NET5 Preview 8, we have introduced a streamlined way for .NET developers to access the set of Windows Runtime (WinRT) APIs that are shipped as part of Windows.
The Go programming language is relatively small and concise, but its depth makes it an ideal option for solving modern-day development problems. In Go Succinctly, author Mark Lewin guides readers through the basics of Go, and he provides documentation and resources that allow users to dive into the language and learn it for themselves. By the end of the book, novices and experienced programmers alike will be conversant in a language quickly gaining traction around the world.
Today we’re happy to announce the availability of the release candidate (RC) of TypeScript 3.1. Our intent with the RC is to gather any and all feedback so that we can ensure our final release is as pleasant as possible.
In any good programming reference, you will read that a developer has to document his code, not only for him/herself, but also for the person who, ten years later will be asked to maintain it. This would, of course, be made easier thanks to a good documentation of existing code.
What’s new for performance in .NET Core and ASP.NET Core 3.0 – Ben Adams
One of the biggest advantages of using .NET Core (besides cross-platform support) is the drastic improvements in performance. Because the .NET Core team was able to make minor breaking changes in the runtime and Base Class Library (BCL), lots of stuff was implemented much more efficiently. In this session Ben will dive into the performance improvements in .NET Core in the 3.0 release: runtime changes, JIT changes, intrinsics and a deep dive into some of the improvements making it the best release yet!
When cloud-based applications use other cloud-based services, errors can occur because of temporary conditions such as intermittent service, infrastructure-level faults, or network issues. Very often, if you retry the operation a short time later (maybe only a few milliseconds later) the operation may succeed
