Subscribe: DotNetGerman Bloggers
http://blogs.dotnetgerman.com/mainfeed.aspx
Added By: Feedage Forager Feedage Grade A rated
Language: German
Tags:
code  component  core  die  eine  electron  für  graphiql  graphql  menu  net core  net  und  von  word word  word 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: DotNetGerman Bloggers

DotNetGerman Bloggers



Alle Blogs von DotNetGerman.com



Copyright: Copyright 2004-2014 DotNetGerman.com
 



Bootstrap 4: Ersatz für die Glyphicons

Thu, 23 Nov 2017 19:52:38 Z

Mit Version 4 wurde in Bootstrap ordentlich aufgeräumt. Unter anderem werden die Glyphicons nicht mehr mitgeliefert. Diese müssen nun ab sofort manuell eingebunden werden. Als Alternative bieten sich auch andere Icon Fonts an. Weit verbreitet und auch von mir immer wieder gerne benutzt ist Font Awesome. Sehr cool an Font Awesome ist: Font Awesome is […]

The post Bootstrap 4: Ersatz für die Glyphicons appeared first on Norbert Eder.




Letzter Beitrag im alten Gewand

Tue, 21 Nov 2017 16:19:03 Z

Liebe Leserschaft, im Rahmen der Erneuerung unserer Firmenwebseite www.aitgmbh.de wurde unser Blog www.tfsblog.de in die neue Webseite integriert: Dies hat zur Folge, dass der bestehende RSS Feed nicht mehr weitergepflegt wird. Im neuen Blog gibt es jedoch wieder die Möglichkeit verschiedenen Themenschwerpunkte zu abonnieren: RSS-Feed “Entwicklung” RSS-Feed “News” RSS-Feed “TFS / DevOps” RSS-Feed “VR / AR […]



Einführung in React, Folge 4: Der Komponenten-Lebenszyklus

Mon, 20 Nov 2017 11:14:00 +0100

Komponenten in React durchlaufen einen komplexen Lebenszyklus, der es ermöglicht, das Verhalten einer Komponente zu verschiedenen Zeitpunkten detailliert zu steuern. Wie funktioniert das, und worauf gilt es dabei zu achten?



News von der österreichischen PowerShell Community

Thu, 16 Nov 2017 06:30:00 Z

Auch wenn der Experts Live Country Event mit über 100 Besuchern den Großteil der Zeit in Anspruch nahm, so war doch auch am Powershell Blog einiges los:



Docker Roadshow in Frankfurt & München

Wed, 15 Nov 2017 11:14:17 Z

Einladung zur Docker MTA Roadshow Warum Sie traditionelle Applikationen modernisieren sollten. IT-Organisationen geben weiterhin 80% ihres Budgets aus um ihre bestehenden Applikationen Aufrecht zu erhalten und nur 20% des Budgets für neue Innovationen. Gemeinsam zeigen Docker und HPE wie sie mit dem Programm „Modernisierung von traditionellen Applikationen“ dazu beitragen können, diese 80% zu eliminieren und...



IEC 61131-3: Unit-Tests

Tue, 14 Nov 2017 22:25:00 Z

Unit-Tests sind ein unentbehrliches Hilfsmittel für jeden Programmierer, um die Funktionsfähigkeit seiner Software sicherzustellen. Programmfehler kosten Zeit und Geld, daher benötigt man eine automatisierte Lösung, um diesen Fehlern auf die Spur zu kommen – und zwar möglichst bevor die Software zum Einsatz kommt. Unit-Tests sollten überall dort eingesetzt werden, wo professionell Software entwickelt wird. Dieser […](image)



.NET 4.7.1 erkennen

Mon, 13 Nov 2017 11:00:00 +0100

Mit dem Erscheinen von .NET Framework 4.7.1 am 19. Oktober 2017 ist eine neue .NET-Version hinzugekommen.



Einladung: Mobile Industry Solutions

Fri, 10 Nov 2017 13:01:23 Z

­ ­ ­ ­ MOBILE INDUSTRY SOLUTIONS 23. November 2017 | Microsoft Österreich, Wien ­ ­ ­ ­ ­ In letzter Zeit werden wir immer wieder gefragt: Wohin geht die Reise in der mobilen Welt? Welche Entwicklungsplattformen und Technologien sollen genutzt werden? Ein Framework – Das kostet doch nur Performance? Wie verwalten wir die mobilen Endgeräte?...



Neu in TFS 2018: Neues für Build und Release Extensions

Fri, 10 Nov 2017 05:00:47 Z

Extensions bieten die Möglichkeiten den TFS um weitere Funktionalität an vordefinierten Stellen, sogenannten Extension Points, zu erweitern. Im Build- und Releasemanagement gibt es hierfür einige Anwendungsfälle: zusätzliche Menüeinträge an Build- und Release Definitionen, eigene Tasks, zusätzliche Informationen in Build- und Release Zusammenfassungen (Build- und Release Summary), u.v.m. In vorhergehenden Beiträgen unserer Blogserie “Neu in TFS […]



Neues Buch zu Windows PowerShell 5.1 und PowerShell Core 6.0

Wed, 08 Nov 2017 11:00:00 +0100

Die Neuauflage von Holger Schwichtenbergs Fachbuch zur PowerShell behandelt nun neben der Windows PowerShell auch die plattformunabhängige PowerShell Core.



Einführung in React, Folge 3: Eingaben verarbeiten

Thu, 02 Nov 2017 10:41:00 +0100

Mit React Eingaben zu verarbeiten ist auf den ersten Blick gar nicht so einfach, denn React kennt zwei Arten von Komponenten, deren Zustandsverwaltung voneinander abweicht. Außerdem gilt es zu steuern, wie Events verteilt werden. Wie funktioniert das?



Herbst Update der österreichischen PowerShell Community

Thu, 02 Nov 2017 08:01:58 Z

Hallo PowerShell Gemeinde! Auch im letzten Monat war einiges los bei uns Künftige Veranstaltungen Experts Live Country Event, 7.11.2017, Microsoft Österreich, http://www.expertslive.at/konferenz.html Experts Live Café Event Linz, 31. Jänner 2018 Experts Live Café Event Wien, 21. März 2018 Vergangene Veranstaltungen Wir hatten 2 sehr spannende und gut besuchte Veranstaltungen. Eine in Wien bei ETC und...



Introducing Electron.NET - building Electron Desktop Apps with ASP.NET Core

Tue, 31 Oct 2017 23:15:00 Z

The last couple of weeks I worked with my buddy Gregor Biswanger on a new project called “Electron.NET“. As you might already guess: It is some sort of bridge between the well known Electron and .NET. If you don’t know what Electron is: It helps to build desktop apps written in HTML/CSS/Javascript The idea Gregor asked me a while ago if it is possible to build desktop apps with ASP.NET Core (or .NET Core in general) and - indeed - there are some ideas how to make it, but unfortunatly there is no “official” UI stack available for .NET Core. After a little chat we agreed that the best bet would be to use Electron as is and somehow “embed” ASP.NET Core in it. I went to bed, but Gregor was keen on to build a prototyp and he did it: He was able to launch the ASP.NET Core application inside the electron app and invoke some Electron APIs from the .NET World. First steps done, yeah! In the following weeks Gregor was able to “bridge” most Electron APIs and I could help him with the tooling via our dotnet-extension. Overview The basic functionality is not too complex: We ship a “standard” (more or less blank) Electron app Inside the Electron part two free ports are searched: The first free port is used inside the Electron app itself The second free port is used for the ASP.NET Core process The app launches the .NET Core process with ASP.NET Core port (e.g. localhost:8002) and injects the first port as parameter Now we have a Socket.IO based linked between the launched ASP.NET Core app and the Electron app itself - this is our communication bridge! At this point you can write your Standard ASP.NET Core Code and can communicate via our Electron.API wrapper to the Electron app. Gregor did a fabulous blogpost with a great example. Interested? This way! If you are interested, maybe take a look at the ElectronNET-Org on GitHub. The complete code is OSS and there are two demo repositories. No way - this is a stupid idea! The last days were quite intersting. We got some nice comments about the project and (of course) there were some critics. As far as I know the current “this is bad, because… “-list is like this: We still need node and Electron.NET is just a wrapper around Electron: Yes, it is. Perf will suck: Well… to be honest - the current startup time does really suck, because we not only launch the Electron stuff, but we also need to start the .NET Core based WebHost - maybe we will find a solution Starting a web server inside the app is bad on multiple levels because of security and perf: I agree, there are some ideas how to fix it, but this might take some time. There are lots of issues open and the project is pretty young, maybe we will find a solution for the above problems, maybe not. Final thoughts The interesting point for me is, that we seem to hit a nerf with this project: There is demand to write X-Plat desktop applications. We are looking for feedback - please share your opinion on the ElectronNET-GitHub-Repo or try it out :) Desktop is dead, long live the desktop![...]



Zeichen in Microsoft SQL Server ersetzen

Tue, 31 Oct 2017 11:00:00 +0100

Während man für mehrere Zeichenersetzungen bisher mehrere verschachtelte Aufrufe der Replace()-Funktion brauchte, geht es seit Microsoft SQL Server 2017 effizienter mit der neuen Translate()-Funktion.



Generating Custom Code with the Angular CLI and Schematics

Sun, 29 Oct 2017 00:00:00 Z

p a { text-decoration: underline } Since some versions, the Angular CLI uses a library called Schematics to scaffold building blocks like components or services. One of the best things about this is that Schematics allows to create own code generators too. Using this extension mechanism, we can modify the way the CLI generates code. But we can also provide custom collections with code generators and publish them as npm packages. A good example for this is Nrwl's Nx which allows to generated boilerplate code for Ngrx or upgrading an existing application from AngularJS 1.x to Angular. These code generators are called Schematics and can not only create new files but also modify existing ones. For instance, the CLI uses the latter to register generated components with existing modules. In this post, I'm showing how to create a collection with a custom Schematic from scratch and how to use it with an Angular project. The sources can be found here. In addition to this, you'll find a nice video with Mike Brocchi from the CLI-Team explaining the basics and ideas behind Schematics here. The public API of Schematics is currently experimental and can change in future. Goal To demonstrate how to write a simple Schematic from scratch, I will build a code generator for a Bootstrap based side menu. With an respective template like the free ones at Creative Tim the result could look like this: Before creating a generator it is a good idea to have an existing solution that contains the code you want to generate in all variations. In our case, the component is quite simple: import { Component, OnInit } from '@angular/core'; @Component({ selector: 'menu', templateUrl: 'menu.component.html' }) export class MenuComponent { } In addition to that, the template for this component is just a bunch of html tags with the right Bootstrap based classes -- something I cannot learn by heart what's the reason a generator seems to be a good idea: In addition to the code shown before, I want also have the possibility to create a more dynamic version of this side menu. This version uses an interface MenuItem to represent the items to display: export interface MenuItem { title: string; iconClass: string; } A MenuService is providing instances of MenuItem: import { MenuItem } from './menu-item'; export class MenuService { public items: MenuItem[] = [ { title: 'Home', iconClass: 'ti-home' }, { title: 'Other Menu Item', iconClass: 'ti-arrow-top-right' }, { title: 'Further Menu Item', iconClass: 'ti-shopping-cart'}, { title: 'Yet another one', iconClass: 'ti-close'} ]; } The component gets an instance of the service by the means of dependency injection: import { Component, OnInit } from '@angular/core'; import { menuItem } from './menu-item'; import { menuService } from './menu.service'; @Component({ selector: 'menu', templateUrl: './menu.component.html', providers:[MenuService] }) export class MenuComponent { items: MenuItem[]; constructor(service: MenuService) { this.items = service.items; } } After fetching the MenuItems from the service the component iterates over them using *ngFor and creates the needed markup:
Neu in TFS 2018: Erweiterungen der Pull Requests

Fri, 27 Oct 2017 04:00:29 Z

Damit der Code einer Software eine hohe Qualität aufweist sind regelmäßige Reviews Pflicht. Pull Requests (PR) bieten für Reviews eine tolle Plattform. Sie stellen eine Art Benachrichtigung dar, in der ein Verantwortlicher Anton eine andere Entwicklerin Berta darum bittet den neuen Code in den bestehenden zu integrieren. Entwicklerin Berta kann nun Feedback liefern und eine […]



Neu in TFS 2018: Jetzt auch mit Git-Forks

Thu, 26 Oct 2017 04:00:32 Z

Mit dem neuen Update halten Git-Forks im TFS 2018 Einzug. Egal ob es der Student oder der Kollege aus einer anderen Abteilung ist, welcher eine neue Funktion implementieren möchte und deshalb Zugriff auf mein Repository benötigt. Mögliche Anwendungsfälle für Git-Forks innerhalb von der TFS-Umgebung gibt es reichlich. Ich, als Besitzer eines Repository möchte nicht, dass […]



GraphiQL for ASP.​NET Core

Thu, 26 Oct 2017 00:00:00 Z

One nice thing about blogging is the feedback from the readers. I got some nice kudos, but also great new ideas. One idea was born out of a question about a "graphi" UI for the GraphQL Middleware I wrote some months ago. I never heard about "graphi", which actually is "GraphiQL", a generic HTML UI over a GraphQL endpoint. It seemed to be something like a Swagger UI, but just for GraphQL. That sounds nice and I did some research about that. What is GraphiQL? Actually it is absolutely not the same as Swagger and not as detailed as Swagger, but it provides a simple and easy to use UI to play around with your GraphQL end-point. So you cannot really compare it. GraphiQL is a React component provided by the GraphQL creators, that can be used in your project. It basically provides an input area to write some GraphQL queries and a button to sent that query to your GrapgQL end-point. You'll than see the result or the error on the right side of the UI. Additionally it provides some more nice features: A history of sent queries, which appears on the left side, if you press the history-button. To reuse previously used queries. It rewrites the URL to support linking to a specific query. It stores the query and the variables in the URL, to sent it to someone else, or to bookmark the query to test. It actually creates a documentation out of the GraphQL end-point. By clicking at the "Docks" link it opens a documentation about the types used in this API. This is really magic, because it shows the documentation of a type I never requested: Implementing GraphiQL The first idea was to write something like this by my own. But it should be the same as the existing GraphiQL UI. Why not using the existing implementation? Thanks to Steve Sanderson, we have the Node Services for ASP.NET Core. Why not running the existing GraphiQL implementation in a Middleware using the NodeServices? I tried it with the "apollo-server-module-graphiql" package. I called this small JavaScript to render the graphiql UI and return it back to C# via the NodeSerices: var graphiql = require('apollo-server-module-graphiql'); module.exports = function (callback, options) { var data = { endpointURL: options.graphQlEndpoint }; var result = graphiql.renderGraphiQL(data); callback(null, result); }; The usage of that script inside the Middleware looks like this: var file = _env.WebRootFileProvider.GetFileInfo("graphiql"); var result = await _nodeServices.InvokeAsync(file.PhysicalPath, _options); await httpCont That works great, but has one problem. It wraps the GraphQL query in a JSON-Object that was posted to the GraphQL end-point. I would need to change the GraphQlMiddleware implementation, because of that. The current implementation expects the plain GraphQL query in the POST body. What is the most useful approach? Wrapping the GraphQL query in a JSON object or sending the plain query? Any Ideas? What do you use? Please tell me by dropping a comment. With this approach I'm pretty much dependent to the Apollo developers and need to change my implementation, whenever they change their implementations. This is why I decided to use the same concept of generating the UI as the "apollo-server-module-graphiql" package but implemented in C#. This unfortunately doesn't need the NodeServices anymore. I use exact the same generated code as this Node module, but changed the way the query is send to the server. Now the plain query will be sent to the server. I started playing around with this and added it to the ex[...]



Deploy a hybrid Kubernetes Cluster to Azure Container Service

Wed, 25 Oct 2017 13:59:39 Z

Lately, I have been working a lot with Kubernetes as one (of many) solutions to run Docker containers in the cloud. Microsoft therefore offers Azure Container Service (ACS), a service to create and (partly) manage a Kubernetes cluster on Azure. You normally would deploy such a cluster via the Azure Portal or e.g. via the ...(image)



Ein nie vollendetes Spiel

Wed, 04 Oct 2017 10:02:00 +0200

Am vergangenen Wochenende begann auf der Webseite nevercompletedgame.com ein Spiel, das die Internet-Community über zahlreiche Stunden auf Trab hielt. Was hat es mit dem Spiel auf sich, und wie lässt es sich lösen?



Git: Add .gitignore after commit

Wed, 04 Oct 2017 06:21:30 Z

I had created a new repository in GitHub and forgot to add the .gitignore file to ignore all my Visual Studio and debugging files. However, I did not realize it until after I created the first commit. These are the steps to apply the gitignore file later: Create a .gitignore file in the root of your […](image)



Neu in TFS 2018: Kleine aber feine Neuerungen im Test Management

Wed, 04 Oct 2017 04:00:12 Z

In der Major Version 2017 des TFS waren eine Vielzahl neuer Features und wesentliche Prozess-Änderungen für den Bereich Testing enthalten. Im Gegensatz dazu konzentriert sich TFS 2018 eher auf kleinere Optimierungen und Neuerungen für bestehende Features. Diese möchten wir Ihnen nicht vorenthalten und laden Sie daher ein, in diesem Beitrag unserer Blogserie „Neu in TFS 2018“, […]



Einführung in React, Folge 1.1: Release von React 16

Mon, 02 Oct 2017 10:47:00 +0200

Vor einigen Tagen hat Facebook eine neue Version von React veröffentlicht, die unter einer anderen Lizenz steht als die bisherigen Versionen. Außerdem wurde die zugrunde liegende Architektur vollständig überarbeitet. Was ist beim Umstieg zu beachten?



Convert all words first letter to upper case (RegEx & Notepad++)

Mon, 02 Oct 2017 00:24:00 -0700

From time to time we need to replace the first letter of many words to the upper case.

String: "word1" "word2" "word3 and/or word4"

Find part: "\b(\w)(\w+)"

Replace part: "\u$1\E$2"

Result: "Word1" "Word2" "Word3 And/Or Word4"


If we want to exclude any word, e.g and, or, so we can make this so:

String: "word1" "word2" "word3 and/or word4"

Find part: "\b(?!and|or)(\w)(\w+)"

Replace part: "\u$1\E$2"

Result: "Word1" "Word2" "Word3 and/or Word4"(image)



dnSpy - a OSS IL decompiler and debugger

Sat, 30 Sep 2017 23:15:00 Z

My colleague was fighting against a nasty bug, that only occures on one machine. Unfortunatly this machine was not a development machine (no VS installed) and we didn’t want to mess with VS remote debugging, because (AFAIK) his would need some additional setup but we were not allowed to install anything.

Soooo… he searched around and found this:

dnSpy - a .NET assembly editor, decompiler, and debugger

The title contains the major points. It is a decompiler, like IL Spy, but addionaly it has a super nice debugger and it looks like a small Visual Studio.

Some pictures how I just decompile Paint.NET and attach the debugger:

(image)

(image)

(image)

I think this is just awesome and it helped my colleague alot.

OSS & Free

The complete project is hosted on GitHub and is “Open Source (GPLv3) and Free Forever”

Checkout the GitHub project page - it contains a lot more information. The tool itself was just 18mb zipped and can be run everywhere.

Its a decompiler!

And just to make sure you keep this in mind: The debugging works with every .NET application (at least in theory), because it decompiles the .NET IL language to C#. It is not a 1:1 debugger, but maybe it can help you.

Check out the dnSpy GitHub Site

(image)



Self Hosted ASP.NET Core: TagHelper doesn’t work

Fri, 29 Sep 2017 06:56:06 Z

I have implemented a simple TagHelper in a ASP.NET Core 2.0 Website, which replace the  



Kostenfreier Xamarin Workshop in Koblenz

Wed, 27 Sep 2017 19:57:04 +0200

Seit einigen Jahren müssen Entwickler einer neuen Herausforderung begegnen. Während die eigene Anwendung in der Vergangenheit in der Regel nur auf einer Plattform, zum Beispiel dem Windows Desktop, oder dem Webbrowser ausgeführt werden musste, besteht heute häufig die die Anforderung auch Clients für mobile Endgeräte auf der Basis von Android, iOS oder Windows zu entwickeln. Dieser Herausforderung kann man mit verschiedenen Lösungsansätzen begegnen: Native Entwicklung mit den Hersteller SDKs, Werkzeugen und Programmiersprachen, also Objective C / Swift und Xcode für iOS, Java / Kotlin und Android Studio für Android und C# / VB.(image)